Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Meteor WebSocket protocol & HTML5

  • 10-08-2010 8:21pm
    #1
    yutta
    Closed Accounts Posts: 429 ✭✭


    What's up with Meteor and HTML5 WebSocket protocol?

    Here's a HTML5 chat demo:

    http://dev.xantus.org/ (note: you need a browser that supports websockets. I.e. Firefox 4 or the development version of Chrome)

    Works fine over my Eircom Wifi connection. Plug in my 3G modem and it won't work: get a red "Disconnected" message.

    The WebSocket (ws://dev.xantus.org) on http://dev.xantus.org/ communicates over port 80 (a port which isn't blocked by Meteor, at least for standard HTML communication).

    I suspect Meteor filter all packets and only allow through certain protocols (e.g. i.e HTML)

    Do O2 and Vodafone have trouble with HTML5 WebSockets?

    Also, tried to register with forums.meteor.ie and they don't support either Firefox or Chrome browsers. I don't have access to Internet Explorer as I'm a Linux user. I log in and when I try to start a new post, it keeps telling me I have to log in confused.gif Nuts.


Comments

  • #2
    Jonathan
    Moderators, Education Moderators, Home & Garden Moderators Posts: 8,260 Mod ✭✭✭✭Jonathan


    It could be something to do with their NAT server, although I'm not privy to their internal network setup.


  • #3
    yutta
    Closed Accounts Posts: 429 ✭✭yutta


    Jonathan wrote: »
    It could be something to do with their NAT server, although I'm not privy to their internal network setup.

    Really? That's interesting.

    I'm doing some NAT myself. I've two IP addresses pointing to the same server. One address (IP address 1) serves pages as usual over port 80, the other (IP address 2) is for websockets over port 80 that's forwarded to port 8000 of IP address 1.

    Would this complicate matters? Gonna go down to O2 tomorrow and try one of their SIMs to see what their network is like. Fingers crossed...


  • #4
    yutta.
    Closed Accounts Posts: 2 ✭yutta.


    Tried port 443. Working fine now. They must be doing something funny on port 80. Would love a full explanation as to what's going on, but my networking knowledge is very limited...


Advertisement