-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
HTTP CONNECT #534
Comments
We can take a PR if you have identified where the issue is. |
In my case, I want to do a proxy chain, so the proxygen has to chain the response is received from upstream. In this case, it should set the headers as it is instead of removing Connection: keep-alive header. Since it seems like a protocol issue. Can you fix this. |
@SteveSelva Where is the Connection: keep-alive header being stripped? Is this happening within the codec when parsing a response? |
@afrind This is happening while generating headers for downstream from the headers received from upstream. The Connection: keep-alive header is stripped at this line: proxygen/proxygen/lib/http/codec/HTTP1xCodec.cpp Lines 565 to 571 in 5c69360
Here they have decided to generate Connection: keep-alive header using the proxygen/proxygen/lib/http/codec/HTTP1xCodec.cpp Lines 439 to 454 in 5c69360
Atlast when the proxygen/proxygen/lib/http/codec/HTTP1xCodec.cpp Lines 676 to 680 in 5c69360
I don't know how to fix this issue properly without impacting the HTTP Protocol. Can you fix it please. |
For HTTP CONNECT request, the Connection: keep-alive header is discarded and Connection: close header is added, even though the Connection: keep-alive header is set in the upstream for 407 status code.
Can you fix this issue.
The text was updated successfully, but these errors were encountered: