Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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] AH03308: ap_proxy_transfer_between_connections: error on sock - ap_get_brigade [Thu Jan 05 11:04:24.002356 2017] [proxy:debug] [pid 65956] proxy_util.c(2169): AH00943: WS: has released connection for (alfred.local) [Thu Jan 05 11:04:28.001195 2017] [proxy:debug] [pid 65946] proxy_util.c(3754): (54)Connection reset by peer: [client 127.0.0.1:51780] AH03308: ap_proxy_transfer_between_connections: error on sock - ap_get_brigade [Thu Jan 05 11:04:28.001369 2017] [proxy:debug] [pid 65946] proxy_util.c(2169): AH00943: WS: has released connection for (alfred.local) Any idea what that might be about and if it is related? 2017-01-05 6:55 GMT-03:00 Yann Ylavic : > 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 ^/(.*)$ wss://backend/$1 [P] > > ProxyPass / https://backend/ > > *But* note that having both HTTP(s) and WS(s) on the same URL it is > *not* recommended, mainly for security reasons. > > While mod_proxy_http is a strict HTTP protocol validator, > mod_proxy_wstunnel is only a tunnel (a TCP proxy) once the upgrade is > asked by the client/browser). > > So with the above configuration a simple Upgrade header in the request > would open a tunnel with backend, including for "normal" HTTP traffic. > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 ^/(.*)$ wss://backend/$1 [P] > ProxyPass / https://backend/ *But* note that having both HTTP(s) and WS(s) on the same URL it is *not* recommended, mainly for security reasons. While mod_proxy_http is a strict HTTP protocol validator, mod_proxy_wstunnel is only a tunnel (a TCP proxy) once the upgrade is asked by the client/browser). So with the above configuration a simple Upgrade header in the request would open a tunnel with backend, including for "normal" HTTP traffic. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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://localhost:8000/chat/stream/ >> >> I get an error in the apache error_log that reads: >> >> No protocol handler was valid for the URL /chat/stream/. If you are using a >> DSO version of mod_proxy, make sure the proxy submodules are included in the >> configuration using LoadModule. >> >> I have read a lot of pages via google of people using this method so I >> wonder if there is some issue in our setup/install of Apache that ships with >> Mac OS X 10.11 & Server.app 5.2? >> >> I have all the standard modules loaded in httpd_server_app.conf >> >> LoadModule proxy_module libexec/apache2/mod_proxy.so >> LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so >> LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so >> >> When I access the application running on localhost:8000 directly on the >> server everything works fine >> >> Any ideas what could be going on? > > There is a bug in this area, but you need to decide what you expect to > happen with non-websockets requests to /chat/stream/ which is what's > happening here. > > If you intend to proxy it, you might need to change the LoadModule > order of mod_proxy_http and mod_proxy_wstunnel to try to get a > different order at runtime. > > If you expect to satisfy it somehow else... you have a bit of a > puzzler. I'm not sure there's a good recipe for this. Otherwise as > Yann said, you should use different URLs if you can. 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 ^/(.*)$ wss://backend/$1 [P] ProxyPass / https://backend/ Actually it didn't work for him because of other app issues (Upgrade missing), but httpd behaved correctly with this. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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". I know nothing about this lib, but from previous logs it seemed that "/chat/stream" was accessed before/without the Upgrade to websocket. Maybe mod_dumpio could be loaded and enabled ("DumpIoIn on" + "DumpIoOutput on"), with "LogLevel trace7", to see the real HTTP data? > > I have just tried: > ProxyPass /chat/ https://localhost:8000/chat/ > ProxyPass /chat/stream wss://localhost:8000/chat/stream > > Now Apache just sits there and nothing loads - > > [Wed Dec 28 12:41:14.523727 2016] [proxy:debug] [pid 45890] > mod_proxy.c(1198): [client 127.0.0.1:62404] AH01143: Running scheme https > handler (attempt 0) > > [Wed Dec 28 12:41:14.523739 2016] [proxy:debug] [pid 45890] > proxy_util.c(2154): AH00942: HTTPS: has acquired connection for (localhost) > > [Wed Dec 28 12:41:14.523749 2016] [proxy:debug] [pid 45890] > proxy_util.c(2208): [client 127.0.0.1:62404] AH00944: connecting > https://localhost:8000/chat/ to localhost:8000 > > [Wed Dec 28 12:41:14.523777 2016] [proxy:debug] [pid 45890] > proxy_util.c(2417): [client 127.0.0.1:62404] AH00947: connected /chat/ to > localhost:8000 > > [Wed Dec 28 12:41:14.523946 2016] [proxy:debug] [pid 45890] > proxy_util.c(2798): (61)Connection refused: AH00957: HTTPS: attempt to > connect to [::1]:8000 (localhost) failed > > [Wed Dec 28 12:41:14.524222 2016] [proxy:debug] [pid 45890] > proxy_util.c(2807): AH02824: HTTPS: connection established with > 127.0.0.1:8000 (localhost) > > [Wed Dec 28 12:41:14.524266 2016] [proxy:debug] [pid 45890] > proxy_util.c(2975): AH00962: HTTPS: connection complete to [::1]:8000 > (localhost) > > [Wed Dec 28 12:41:14.524283 2016] [ssl:info] [pid 45890] [remote > 127.0.0.1:8000] AH01964: Connection to child 0 established (server > alfred.local:80) Nothing wrong here, no further error? Probably LogLevel trace7 (and mod_dumpio) could tell more. > > Browser > Proxy Error > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request GET /chat/. > Reason: Error reading from remote server Hmm, is //localhost:8000/chat/ expecting https traffic? Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 expected to happen is that proxypass would catch the urls that contain /chat/stream and proxy them to the app running on localhost:8000 via the wss:// protocol - all other http/s traffic handled by the app running via mod_wsgi. I have just tried: ProxyPass /chat/ https://localhost:8000/chat/ ProxyPass /chat/stream wss://localhost:8000/chat/stream Now Apache just sits there and nothing loads - [Wed Dec 28 12:41:14.523727 2016] [proxy:debug] [pid 45890] mod_proxy.c(1198): [client 127.0.0.1:62404] AH01143: Running scheme https handler (attempt 0) [Wed Dec 28 12:41:14.523739 2016] [proxy:debug] [pid 45890] proxy_util.c(2154): AH00942: HTTPS: has acquired connection for (localhost) [Wed Dec 28 12:41:14.523749 2016] [proxy:debug] [pid 45890] proxy_util.c(2208): [client 127.0.0.1:62404] AH00944: connecting https://localhost:8000/chat/ to localhost:8000 [Wed Dec 28 12:41:14.523777 2016] [proxy:debug] [pid 45890] proxy_util.c(2417): [client 127.0.0.1:62404] AH00947: connected /chat/ to localhost:8000 [Wed Dec 28 12:41:14.523946 2016] [proxy:debug] [pid 45890] proxy_util.c(2798): (61)Connection refused: AH00957: HTTPS: attempt to connect to [::1]:8000 (localhost) failed [Wed Dec 28 12:41:14.524222 2016] [proxy:debug] [pid 45890] proxy_util.c(2807): AH02824: HTTPS: connection established with 127.0.0.1:8000 (localhost) [Wed Dec 28 12:41:14.524266 2016] [proxy:debug] [pid 45890] proxy_util.c(2975): AH00962: HTTPS: connection complete to [::1]:8000 (localhost) [Wed Dec 28 12:41:14.524283 2016] [ssl:info] [pid 45890] [remote 127.0.0.1:8000] AH01964: Connection to child 0 established (server alfred.local:80) *Browser* Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /chat/. Reason: Error reading from remote server 2016-12-28 11:57 GMT-03:00 Eric Covener : > 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://localhost:8000/chat/stream/ > >> > >> I get an error in the apache error_log that reads: > >> > >> No protocol handler was valid for the URL /chat/stream/. If you are > using a > >> DSO version of mod_proxy, make sure the proxy submodules are included > in the > >> configuration using LoadModule. > >> > >> I have read a lot of pages via google of people using this method so I > >> wonder if there is some issue in our setup/install of Apache that ships > with > >> Mac OS X 10.11 & Server.app 5.2? > >> > >> I have all the standard modules loaded in httpd_server_app.conf > >> > >> LoadModule proxy_module libexec/apache2/mod_proxy.so > >> LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so > >> LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so > >> > >> When I access the application running on localhost:8000 directly on the > >> server everything works fine > >> > >> Any ideas what could be going on? > > > > There is a bug in this area, but you need to decide what you expect to > > happen with non-websockets requests to /chat/stream/ which is what's > > happening here. > > > > If you intend to proxy it, you might need to change the LoadModule > > order of mod_proxy_http and mod_proxy_wstunnel to try to get a > > different order at runtime. > > > > If you expect to satisfy it somehow else... you have a bit of a > > puzzler. I'm not sure there's a good recipe for this. Otherwise as > > Yann said, you should use different URLs if you can. > > Yann pointed out that the shareing is doomed for other reasons, so > disregard the above! > > -- > Eric Covener > cove...@gmail.com > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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://localhost:8000/chat/stream/ >> >> I get an error in the apache error_log that reads: >> >> No protocol handler was valid for the URL /chat/stream/. If you are using a >> DSO version of mod_proxy, make sure the proxy submodules are included in the >> configuration using LoadModule. >> >> I have read a lot of pages via google of people using this method so I >> wonder if there is some issue in our setup/install of Apache that ships with >> Mac OS X 10.11 & Server.app 5.2? >> >> I have all the standard modules loaded in httpd_server_app.conf >> >> LoadModule proxy_module libexec/apache2/mod_proxy.so >> LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so >> LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so >> >> When I access the application running on localhost:8000 directly on the >> server everything works fine >> >> Any ideas what could be going on? > > There is a bug in this area, but you need to decide what you expect to > happen with non-websockets requests to /chat/stream/ which is what's > happening here. > > If you intend to proxy it, you might need to change the LoadModule > order of mod_proxy_http and mod_proxy_wstunnel to try to get a > different order at runtime. > > If you expect to satisfy it somehow else... you have a bit of a > puzzler. I'm not sure there's a good recipe for this. Otherwise as > Yann said, you should use different URLs if you can. Yann pointed out that the shareing is doomed for other reasons, so disregard the above! -- Eric Covener cove...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 error_log that reads: > > No protocol handler was valid for the URL /chat/stream/. If you are using a > DSO version of mod_proxy, make sure the proxy submodules are included in the > configuration using LoadModule. > > I have read a lot of pages via google of people using this method so I > wonder if there is some issue in our setup/install of Apache that ships with > Mac OS X 10.11 & Server.app 5.2? > > I have all the standard modules loaded in httpd_server_app.conf > > LoadModule proxy_module libexec/apache2/mod_proxy.so > LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so > LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so > > When I access the application running on localhost:8000 directly on the > server everything works fine > > Any ideas what could be going on? There is a bug in this area, but you need to decide what you expect to happen with non-websockets requests to /chat/stream/ which is what's happening here. If you intend to proxy it, you might need to change the LoadModule order of mod_proxy_http and mod_proxy_wstunnel to try to get a different order at runtime. If you expect to satisfy it somehow else... you have a bit of a puzzler. I'm not sure there's a good recipe for this. Otherwise as Yann said, you should use different URLs if you can. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 (attempt 0) > > Looks like the request is missing the "Upgrade: WebSocket" header, > which mod_proxy_wstunnel requires. > > From your configuration: > ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/ > it seems that /chat/stream/ is used for "normal" HTTP traffic (before > the upgrade to WebSocket, possibly). > > Couldn't the pure WebSocket things be handled by another (inner) URL > instead, so that the following could work: > ProxyPass /chat/stream/ https://localhost:8000/chat/stream/ > ProxyPass /chat/stream/wss wss://localhost:8000/chat/stream/wss > Seems like we should setup wstunnel to go before http, so you could then just configure both proxypasses and wstunnell would defer. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 (attempt 0) > > Looks like the request is missing the "Upgrade: WebSocket" header, > which mod_proxy_wstunnel requires. That was the relevant log (rather than the above): >> [Wed Dec 28 09:31:05.974773 2016] [proxy_wstunnel:debug] [pid 27844] >> mod_proxy_wstunnel.c(299): [client 127.0.0.1:54002] AH02900: declining URL >> wss://127.0.0.1:8000/chat/stream/ (not WebSocket) - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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: WebSocket" header, which mod_proxy_wstunnel requires. >From your configuration: ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/ it seems that /chat/stream/ is used for "normal" HTTP traffic (before the upgrade to WebSocket, possibly). Couldn't the pure WebSocket things be handled by another (inner) URL instead, so that the following could work: ProxyPass /chat/stream/ https://localhost:8000/chat/stream/ ProxyPass /chat/stream/wss wss://localhost:8000/chat/stream/wss ? Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 2016] [authz_core:debug] [pid 27844] mod_authz_core.c(834): [client 127.0.0.1:54002] AH01628: authorization result: granted (no directives) [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) [Wed Dec 28 09:31:05.974756 2016] [proxy_http:debug] [pid 27844] mod_proxy_http.c(1893): [client 127.0.0.1:54002] AH01113: HTTP: declining URL wss://127.0.0.1:8000/chat/stream/ [Wed Dec 28 09:31:05.974765 2016] [proxy_scgi:debug] [pid 27844] mod_proxy_scgi.c(537): [client 127.0.0.1:54002] AH00865: declining URL wss://127.0.0.1:8000/chat/stream/ [Wed Dec 28 09:31:05.974773 2016] [proxy_wstunnel:debug] [pid 27844] mod_proxy_wstunnel.c(299): [client 127.0.0.1:54002] AH02900: declining URL wss://127.0.0.1:8000/chat/stream/ (not WebSocket) [Wed Dec 28 09:31:05.976075 2016] [proxy_ajp:debug] [pid 27844] mod_proxy_ajp.c(738): [client 127.0.0.1:54002] AH00894: declining URL wss:// 127.0.0.1:8000/chat/stream/ [Wed Dec 28 09:31:05.976088 2016] [proxy:warn] [pid 27844] [client 127.0.0.1:54002] AH01144: No protocol handler was valid for the URL /chat/stream/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are include 2016-12-27 16:10 GMT-03:00 Adam Teale : > 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:readWriteSettingsVersion = 1 > > web:apacheVersion = "2.2" > > web:servicePortsRestrictionInfo = _empty_array > > web:startedTime = "2016-12-27 19:08:59 +" > > web:apacheState = "RUNNING" > > web:statusMessage = "" > > web:ApacheMode = 2 > > web:servicePortsAreRestricted = "NO" > > web:state = "STOPPED" > > web:setStateVersion = 1 >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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:readWriteSettingsVersion = 1 web:apacheVersion = "2.2" web:servicePortsRestrictionInfo = _empty_array web:startedTime = "2016-12-27 19:08:59 +" web:apacheState = "RUNNING" web:statusMessage = "" web:ApacheMode = 2 web:servicePortsAreRestricted = "NO" web:state = "STOPPED" web:setStateVersion = 1
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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? > > 2016-12-27 11:28 GMT-03:00 Adam Teale : > >> Hi Otis thanks for looking into it for me. >> The link to revathskumar's blog is pretty much what I have setup at the >> moment. I'll check out the bug report! Thanks! >> >> 2016-12-27 11:23 GMT-03:00 Otis Dewitt - NOAA Affiliate < >> otis.dew...@noaa.gov>: >> >>> 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 interesting though that when I run an "sudo apachectl -M" i can't see ssl_module in there. >>> >>> >> >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 interesting though that when I run an "sudo apachectl -M" i can't > see ssl_module in there. > > > >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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 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/stream/ >> >> I get an error in the apache error_log that reads: >> >> No protocol handler was valid for the URL /chat/stream/. If you are using >> a DSO version of mod_proxy, make sure the proxy submodules are included in >> the configuration using LoadModule. >> >> I have read a lot of pages via google of people using this method so I >> wonder if there is some issue in our setup/install of Apache that ships >> with Mac OS X 10.11 & Server.app 5.2? >> >> I have all the standard modules loaded in httpd_server_app.conf >> >> LoadModule proxy_module libexec/apache2/mod_proxy.so >> LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so >> LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so >> >> When I access the application running on localhost:8000 directly on the >> server everything works fine >> >> Any ideas what could be going on? >> >> Thanks! >> >> Adam >> Apache 2.4.18, Mac OS X 10.11, Server.app 5.2 >> > > > > -- > *Daniel Ferradal* > IT Specialist > > email dferradal at gmail.com > linkedin es.linkedin.com/in/danielferradal >
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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.
Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
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/stream/ > > I get an error in the apache error_log that reads: > > No protocol handler was valid for the URL /chat/stream/. If you are using > a DSO version of mod_proxy, make sure the proxy submodules are included in > the configuration using LoadModule. > > I have read a lot of pages via google of people using this method so I > wonder if there is some issue in our setup/install of Apache that ships > with Mac OS X 10.11 & Server.app 5.2? > > I have all the standard modules loaded in httpd_server_app.conf > > LoadModule proxy_module libexec/apache2/mod_proxy.so > LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so > LoadModule proxy_wstunnel_module libexec/apache2/mod_proxy_wstunnel.so > > When I access the application running on localhost:8000 directly on the > server everything works fine > > Any ideas what could be going on? > > Thanks! > > Adam > Apache 2.4.18, Mac OS X 10.11, Server.app 5.2 > -- *Daniel Ferradal* IT Specialist email dferradal at gmail.com linkedin es.linkedin.com/in/danielferradal