On Tue, Jul 4, 2023 at 2:28 AM Helmut K. C. Tessarek <tessa...@evermeet.cx> wrote: > > The documentation states: > > Proxying both HTTP and websockets at the same time, where the websockets URL's > are not websocket-only or not known in advance can be done by using the > RewriteRule directive to configure the websockets proxying: > > ProxyPass / http://example.com:9080/ > RewriteEngine on > RewriteCond %{HTTP:Upgrade} websocket [NC] > RewriteCond %{HTTP:Connection} upgrade [NC] > RewriteRule ^/?(.*) "ws://example.com:9080/$1" [P,L] > > However, I was wondering, whether the following is an equivalent directive > (just in a single line ;-)): > > ProxyPass / http://example.com:9080/ upgrade=websocket > > afaik the upgrade only takes place when it is requested by a header, unless > upgrade=NONE or upgrade=ANY is set. > > Am I correct or are the not the same?
Yes, they should be the same. Upgrade only takes place when requested AND accepted/switched by the backend server. Regards; Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org