https://bz.apache.org/bugzilla/show_bug.cgi?id=65286
--- Comment #2 from Yann Ylavic <ylavic....@gmail.com> --- > This is a minimal proxy configuration which shows the issue: > > <IfModule mod_proxy.c> > ProxyRequests On > <Proxy *> > Require ip 192.168.1.0/255.255.255.0 127.0.0.0/255.0.0.0 ::1 > </Proxy> > </IfModule> It tried that with firefox and it seems that websocket.org issues a "CONNECT echo.websocket.org:80 HTTP/1.1" request when clicking on the "connect" button (port 80 or 443 depending on schemes ws: or wss: respectively). So it works for me with: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_connect_module modules/mod_proxy_connect.so AllowCONNECT 80 443 ProxyRequests On <Proxy *> Require ip ... </Proxy> But I agree that a "GET http://echo.websocket.org:80/ HTTP/1.1" request wouldn't work with WebSocket because the generic forward proxy worker does not handle Upgrade for now. Not sure it's worth it though with nowadays TLS everywhere.. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
