Initially I thought this was a bug from the Jetty HttpClient Java library, after I filled out a bug report and things were checked into we found out that Fiddler proxy replies to the CONNECT with a response that contains Connection: close.
I tried to capture the same traffic in Charles and it's working with no issues. Here is the link to my Jetty bug report page.
https://github.com/eclipse/jetty.project/issues/973#issuecomment-250836144
Here is the link to the log file http://dropcanvas.com/11ltw
Any idea why it's working fine in Charles but not in Fiddler?
1 Answer, 1 is accepted
0
Hello,
That seems to be a bug in Jetty indeed. Connection:close does not mean close the connection after getting the response to CONNECT request. This is a good discussion on the subject - http://stackoverflow.com/questions/22875092/why-fiddler-adds-connectionclose-on-connect-response. There are many others, too. Eric Lawrence did a good job explaining that a couple of times.
So while waiting for a fix as a workaround you could remove the Connection header with FiddlerScript before sending the reply to the client.
Regards,
Tsviatko Yovtchev
Telerik by Progress
That seems to be a bug in Jetty indeed. Connection:close does not mean close the connection after getting the response to CONNECT request. This is a good discussion on the subject - http://stackoverflow.com/questions/22875092/why-fiddler-adds-connectionclose-on-connect-response. There are many others, too. Eric Lawrence did a good job explaining that a couple of times.
So while waiting for a fix as a workaround you could remove the Connection header with FiddlerScript before sending the reply to the client.
Regards,
Tsviatko Yovtchev
Telerik by Progress
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items