Apache doesn't correctly proxy the websockets upgrade requests so a socket never gets established.
On 7 March 2012 18:26, Ben Hegarty <[email protected]> wrote: > Bit of a dumb question then, where exactly is the problem... > Is it that the apache server has a bug when supporting websockets? Or is it > that WIAB isn't playing correctly with the protocol? jjust so I can follow > up I suppose... > > On Wed, Mar 7, 2012 at 4:12 PM, Yuri Z <[email protected]> wrote: > >> Yep, just uses port 80. >> >> On Wed, Mar 7, 2012 at 6:10 PM, Bruno Gonzalez <[email protected]> wrote: >> >> > What does waveinabox.net use? >> > Or is it simply using port 80 instead of the default? >> > >> > On Wed, Mar 7, 2012 at 16:33, Vicente J. Ruiz Jurado < >> [email protected] >> > >wrote: >> > >> > > El 07/03/12 15:26, Cathy Taylor escribió: >> > > > My experience with running it that way is websockets don't get >> proxied >> > > through Apache. I haven't found a resolution and the workarounds I >> found >> > > didn't work for me. Only Firefox worked when running it with Apache in >> > > front. >> > > > >> > > > -Cathy >> > > > >> > > >> > > Maybe you can try with nginx: >> > > https://github.com/LearnBoost/socket.io/wiki/Nginx-and-Socket.io >> > > >> > > Bests, >> > > -- >> > > Vicente J. Ruiz Jurado >> > > >> > > http://comunes.org >> > > http://ourproject.org >> > > http://homes.ourproject.org/~vjrj/blog (@vjrj) >> > > >> > > "The preservation of the means of knowledge among the lowest ranks is >> > > of more importance to the public than all the property of the rich men >> > > in the country." [John Adams (1735-1826)] >> > > >> > > >> > > >> > > >> > > >> > > >> > >> > >> > -- >> > Saludos, >> > Bruno González >> > >> > _______________________________________________ >> > Jabber: stenyak AT gmail.com >> > http://www.stenyak.com >> > >> > > > > -- > blog:http://thelifeofbenhegs.blogspot.com/ > phone: +447767-322-122
