HTTPS requests without host:port get assigned to a different connection than the one opened with the initial CONNECT

Question

HTTPS requests without host:port get assigned to a different connection than the one opened with the initial CONNECT

oxtoacart opened this issue 11 years ago · 1 comments

oxtoacart commented 11 years ago

Things work correctly if the browser issues requests like these:

CONNECT thehost:9000
GET thehost:9000/resource_on_the_host

However, if the browser issues requests like these, the 2nd get will result in an attempt to open a new connection:

CONNECT thehost:9000
GET /resource_on_the_host

Answer 1 · 2013-09-22T22:17:12.000Z

This was a false alarm - the branch in which we look up a connection only happens for the first HttpRequest, which doesn't apply when we're tunneling.