-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11845. WebAppProxy add Connection close header to prevent CLOSE_WAIT leaks #8697
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
Open
sohurdc
wants to merge
3
commits into
apache:trunk
Choose a base branch
from
sohurdc:YARN-11845
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+102
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also changes the client-facing connection behavior.
proxyLink()copies every header from the upstream response intoresp, so when the AM/history server responds withConnection: close, that hop-by-hop header is forwarded to the browser/API client as well.I verified this by checking
proxyConn.getHeaderField("Connection")in the new test, and the client-facing response containsclose.Consequently, every proxied request loses keep-alive between the client and WebAppProxy, contrary to the PR description that only the internal connection is affected. RFC 9110 Section 7.6.1 also requires intermediaries to remove
Connectionand other connection-specific fields before forwarding.Could we instead close the locally created
CloseableHttpClient/CloseableHttpResponsewith try-with-resources, which directly addresses the resource lifecycle? If the request header is retained, the response path should filter hop-by-hop headers and the test should verify that the client-facing connection is not forced closed.