Hi Yann thanks again for all your help.
I am still trying to work out why the client isn't receiving the Upgrade
header in the response.
I see a proxy debug log:
[Thu Jan 05 11:04:24.002173 2017] [proxy:debug] [pid 65956]
proxy_util.c(3754): (54)Connection reset by peer: [client 127.0.0.1:51776]
On Thu, Jan 5, 2017 at 10:36 AM, Yann Ylavic wrote:
>
> For the record (after private discussion with Adam), it seems that a
> configuration like the below would work for http(s) and ws(s) on the
> same URL:
>
> RewriteEngine on
> RewriteCond %{HTTP:Upgrade} "(?i)websocket"
> RewriteRule ^/(
On Wed, Dec 28, 2016 at 3:53 PM, Eric Covener wrote:
> On Tue, Dec 27, 2016 at 8:39 AM, Adam Teale wrote:
>> Hi!
>>
>> I've been trying to setup a reverse proxy to a localhost websocket url.
>>
>> ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
>> ProxyPassReverse /chat/stream/ wss://lo
On Wed, Dec 28, 2016 at 4:47 PM, Adam Teale wrote:
>
> As far as I know the "normal" http traffic is via "/chat/" (well at least
> that is visited page url).
>
> When that page loads is connects to "/chat/stream" via the wss:// protocol
> using a javascript library called "reconnecting-websocket".
Yann & Eric thank you for getting back to me.
As far as I know the "normal" http traffic is via "/chat/" (well at least
that is visited page url).
When that page loads is connects to "/chat/stream" via the wss:// protocol
using a javascript library called "reconnecting-websocket".
So what I have
On Wed, Dec 28, 2016 at 9:53 AM, Eric Covener wrote:
> On Tue, Dec 27, 2016 at 8:39 AM, Adam Teale wrote:
>> Hi!
>>
>> I've been trying to setup a reverse proxy to a localhost websocket url.
>>
>> ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
>> ProxyPassReverse /chat/stream/ wss://lo
On Tue, Dec 27, 2016 at 8:39 AM, Adam Teale wrote:
> Hi!
>
> I've been trying to setup a reverse proxy to a localhost websocket url.
>
> ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
> ProxyPassReverse /chat/stream/ wss://localhost:8000/chat/stream/
>
> I get an error in the apache err
On Wed, Dec 28, 2016 at 9:21 AM, Yann Ylavic wrote:
> On Wed, Dec 28, 2016 at 1:32 PM, Adam Teale wrote:
>> more detail from the error log:
>>
>> [Wed Dec 28 09:31:05.974744 2016] [proxy:debug] [pid 27844]
>> mod_proxy.c(1198): [client 127.0.0.1:54002] AH01143: Running scheme wss
>> handler (atte
On Wed, Dec 28, 2016 at 3:21 PM, Yann Ylavic wrote:
> On Wed, Dec 28, 2016 at 1:32 PM, Adam Teale wrote:
>> more detail from the error log:
>>
>> [Wed Dec 28 09:31:05.974744 2016] [proxy:debug] [pid 27844]
>> mod_proxy.c(1198): [client 127.0.0.1:54002] AH01143: Running scheme wss
>> handler (atte
On Wed, Dec 28, 2016 at 1:32 PM, Adam Teale wrote:
> more detail from the error log:
>
> [Wed Dec 28 09:31:05.974744 2016] [proxy:debug] [pid 27844]
> mod_proxy.c(1198): [client 127.0.0.1:54002] AH01143: Running scheme wss
> handler (attempt 0)
Looks like the request is missing the "Upgrade: WebS
more detail from the error log:
[Wed Dec 28 09:31:05.974520 2016] [remoteip:debug] [pid 27844]
mod_remoteip.c(357): [client 127.0.0.1:54002] AH01569: RemoteIP: Header
X-Forwarded-For value of fe80::761b:b2ff:feda:99e7 appears to be a private
IP or nonsensical. Ignored
[Wed Dec 28 09:31:05.974700
Perhaps something useful - I do see that the "serveradmin" command says
that it runs apache 2.2 even though "httpd -v" says 2.4.23??
httpd -v
Server version: Apache/2.4.23 (Unix)
Server built: Aug 8 2016 16:31:34
sudo serveradmin fullstatus web
web:health = _empty_dictionary
web:readWri
I have upgraded to MacOS 10.12 so now Apache 2.4.23 is the current version.
Either way the patch that was suggested was supposed to have been included
in 2.4.10.
2016-12-27 11:29 GMT-03:00 Adam Teale :
> Otis do you know if it pretty straightforward to apply a patch to an
> apache module?
>
> 2
You can also check this URL:
http://blog.revathskumar.com/2015/09/proxy-websocket-via-apache.html
Thanks,
Otis
On Tue, Dec 27, 2016 at 9:07 AM, Adam Teale wrote:
> Hi Daniel,
>
> Yes in the http_server_app.conf file it is activated:
> LoadModule ssl_module libexec/apache2/mod_ssl.so
>
> It is
Check this link out.
http://stackoverflow.com/questions/17889676/apache-2-4-6-reverseproxy-mod-proxy-wstunnel-for-secure-websocket-wss-fails
Thanks,
Otis
On Tue, Dec 27, 2016 at 8:55 AM, Daniel wrote:
> Silly question perhaps, are you also loading mod_ssl?
>
> 2016-12-27 14:39 GMT+01:00 Adam T
Hi Daniel,
Yes in the http_server_app.conf file it is activated:
LoadModule ssl_module libexec/apache2/mod_ssl.so
It is interesting though that when I run an "sudo apachectl -M" i can't
see ssl_module in there.
Silly question perhaps, are you also loading mod_ssl?
2016-12-27 14:39 GMT+01:00 Adam Teale :
> Hi!
>
> I've been trying to setup a reverse proxy to a localhost websocket url.
>
> ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
> ProxyPassReverse /chat/stream/ wss://localhost:8000/chat/
Hi!
I've been trying to setup a reverse proxy to a localhost websocket url.
ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
ProxyPassReverse /chat/stream/ wss://localhost:8000/chat/stream/
I get an error in the apache error_log that reads:
No protocol handler was valid for the URL /ch
18 matches
Mail list logo
