On 06/15/2011 05:51 PM, Subbu Allamaraju wrote:
I'm using TS as a reverse proxy to test protocol upgrade requests. The client
is sending the following headers
Host:localhost
Connection:Upgrade
Origin:http://localhost
Sec-WebSocket-Key1:3B 5 40c3=2J712
Sec-WebSocket-Key2:2z 79 9 9 2 8730
Upgrade:WebSocket
and I noticed that the proxy is not relaying Connection and Upgrade headers. Is
there a way to influence the list of headers?
Hi Subbu,
sorry for the late reply. Did you get this resolved yet? If not, I'll
try to take a look at it tomorrow, and see if there's anything to do
about conveying those headers upstream.
On a broader note, can traffic server deal with protocol upgrade requests?
As far as I know, there's nothing in our code that deals with
"upgrades", but I'm not certain. Wouldn't upgrades be protocol specific
in general? ATS doesn't have any direct support for WebSocket's, yet at
least :).
Cheers,
-- Leif
