Hello Marc, On Wed, Apr 15, 2015 at 10:50 AM, Marc Hörsken <i...@marc-hoersken.de> wrote: > > Now once a browser has upgraded a connection from HTTP to WebSocket traffic, > all traffic is proxied to the WebSocket-server at 127.0.0.1:9001. The > problem is that the browser continues to use that upgraded > WebSocket-connection for further HTTP-requests, for example to load the next > page. > > But since all traffic is forwarded to the WebSocket-server, the browser > receives a 404 from there. So for some reason HTTP- and > WebSocket-connections are not isolated properly. And Apache2 forwards URLs > not beginning with /data or /settings.js to the Web-Socket-server. > > Any ideas why this might happen?
Once the connection is upgraded, mod_proxy_wstunnel (as its name suggests) creates a tunnel between the browser and the application. It will not check requests boundaries anymore, this is not HTTP but application data now, and hence application's responsability to not (make the browser) reuse the same connection for further HTTP requests. Regards, Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
