it gets executed first.
Manpreet
*From:* jetty-users-boun...@eclipse.org *On
Behalf Of *Joakim Erdfelt
*Sent:* Thursday, October 1, 2020 5:10 AM
*To:* JETTY user mailing list
*Subject:* Re: [jetty-users] Issue with Jetty Web Sockets behind IIS
Reverse Proxy
This wouldn't be the first
This wouldn't be the first time we've received reports about IIS messing
with the websocket upgrade request headers before it reaches Jetty.
Check the headers at the Jetty side, make sure they have the following
present (to be a valid WebSocket upgrade request).
This is documented in https://tools
Hi Manpreet,
If we remove IIS in front of Jetty 9.4.24 it works as well.
If we upgrade Jetty to latest version 9.4.31 it doesn’t work.
Does it also work on 9.4.31 when not using IIS in front of jetty?
Firstly it would be useful to see what the HTTP websocket upgrade request
looks like when it
Hi,
We have a setup where Jetty sits behind an Microsoft IIS Reverse Proxy (via
ARR). IIS is 10.5 on Windows 2019. Our Web application deployed in Jetty
uses web sockets to render video on the browser.
Since we have upgraded from Jetty 9.2.17.v20160517 to 9.4.24.v20191120,
the web socket see
