Setup WIAB behind an apache server

2012-03-07 Thread Ben Hegarty
Hi Guys, Recently I've been trying to set up a WIAB server behind an apache server by forwarding the wave.mydomain.com subdomain to the 9898 port in WIAB, it seems to be ok accept for the fact that when I log in I can't see new waves in the inbox and the welcome wave never loads.. The apache

Re: Setup WIAB behind an apache server

2012-03-07 Thread Cathy Taylor
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 On Mar 7, 2012, at 8:54 AM, Ben Hegarty wrote: Hi Guys,

Re: Setup WIAB behind an apache server

2012-03-07 Thread Bruno Gonzalez
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 v...@ourproject.orgwrote: El 07/03/12 15:26, Cathy Taylor escribió: My experience with running it that way is websockets don't get proxied through Apache.

Re: Setup WIAB behind an apache server

2012-03-07 Thread Yuri Z
Yep, just uses port 80. On Wed, Mar 7, 2012 at 6:10 PM, Bruno Gonzalez sten...@gmail.com 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 v...@ourproject.org wrote: El 07/03/12 15:26, Cathy

Re: Setup WIAB behind an apache server

2012-03-07 Thread Ben Hegarty
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 vega...@gmail.com wrote:

Re: Setup WIAB behind an apache server

2012-03-07 Thread Ali Lown
Apache doesn't correctly proxy the websockets upgrade requests so a socket never gets established. On 7 March 2012 18:26, Ben Hegarty heg...@gmail.com 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

Review Request: Gadget size not setted when metadata cached

2012-03-07 Thread vjrj
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4234/ --- Review request for wave. Summary --- I was debugging a little bit and I

Re: Setup WIAB behind an apache server

2012-03-07 Thread Greg Tangey
I'm running mine on port 80 with some ip-tables redirects. From what I've read that's probably the best way to get it running on Port 80 for now. On 08/03/2012, at 12:12 AM, Yuri Z wrote: Yep, just uses port 80. On Wed, Mar 7, 2012 at 6:10 PM, Bruno Gonzalez