Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
oxtoacart opened this issue Sep 20, 2013 · 1 comment
Milestone

Comments

@oxtoacart
Copy link
Collaborator

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

@oxtoacart
Copy link
Collaborator Author

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.

MediumOne pushed a commit to MediumOne/LittleProxy that referenced this issue Jun 7, 2022
…logging.log4j-log4j-core-2.15.0

Bump log4j-core from 2.14.0 to 2.15.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant