Configure a VirtualHost on Apache for Wave. Or use another port by
defining it in your Wave server config file.
On 16/05/12 12:27, 李向彬 wrote:
how can i do that since apache already taken the port:80?
On Wed, May 16, 2012 at 5:42 PM, Yuri Z vega...@gmail.com wrote:
You can set the port to 80
Also, you can use other software like HAProxy listening on 80 and
redirecting either to Apache or any other HTTP servers running on the
localhost or other remote services. I for one would prefer this approach
(and actually I have it implemented) to find your way with Apache
VirtualHosts.
On
.
http_frontend_addresses = wave.example.com:9898
-Original Message-
From: 李向彬 [mailto:dannyalansh...@gmail.com]
Sent: Wednesday, 16 May 2012 7:27 PM
To: wave-dev@incubator.apache.org
Subject: Re: Setup WIAB behind an apache server
how can i do that since apache already taken the port:80?
On Wed
To: wave-dev@incubator.apache.org
Subject: Re: Setup WIAB behind an apache server
how can i do that since apache already taken the port:80?
On Wed, May 16, 2012 at 5:42 PM, Yuri Z vega...@gmail.com wrote:
You can set the port to 80 in the server.config. But you would need
El 07/03/12 14:54, Ben Hegarty escribió:
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
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
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,
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.
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
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:
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
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
12 matches
Mail list logo
