-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8263442: Potential bug in jdk.internal.net.http.common.Utils.CONTEXT_RESTRICTED #2977
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
Conversation
👋 Welcome back michaelm! A progress list of the required criteria for merging this PR into |
@Michael-Mc-Mahon The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
if (reqh.containsKey("authorization")) { | ||
e.sendResponseHeaders(500, -1); |
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.
I am a bit concerned by that. It shows that without your fix preemptive authentication would have worked, as the server would have received the authorization header.
I did a bit of an experiment - and it seems that with proxy-authorization you would get an IOException (with or without your fix). So it seems that without your fix we are unwillingly currently supporting user preemptive authentication (for servers) in the presence of an authenticator, but not for proxies. With your fix, neither will be supported.
Is that the right thing to do?
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.
What I am seeing is that if no authenticator set, whether the fix is present or not, an "Authorization" header is passed through, but a "Proxy-Authorization" header is filtered. So, that is a different issue. It probably is a bug though.
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.
I've updated the test to test the proxy authorization case
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.
Don't you need to set -Djdk.http.auth.proxying.disabledSchemes=""
on the command line to have a chance that Proxy-Authorization will be forwarded?
if (reqh.containsKey("authorization")) { | ||
e.sendResponseHeaders(500, -1); |
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.
Don't you need to set -Djdk.http.auth.proxying.disabledSchemes=""
on the command line to have a chance that Proxy-Authorization will be forwarded?
@Michael-Mc-Mahon This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 77 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
||
if (useProxy) { | ||
builder.proxy(ProxySelector.of(proxyAddr)); | ||
} |
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.
You should probably set NO_PROXY otherwise to avoid the default proxy selector on mac.
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.
For the non-proxy case? Good idea.
Regarding the question above about the -Djdk.http.auth.proxying.disabledSchemes=""
setting. The test fails for both server and proxy auth without this change (and without having to set that property).
String authHdr; | ||
if (useProxy) { | ||
proxy = new ProxyServer(); | ||
proxyAddr = new InetSocketAddress("127.0.0.1", proxy.getPort()); |
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.
Maybe the test should be guarded in case the machine is IPv6 only
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.
Okay, will fix that too.
/integrate |
@Michael-Mc-Mahon Since your change was applied there have been 79 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit bd7a184. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
The fix for the reported bug in Utils.CONTEXT_RESTRICTED caused a couple of regression failures, which turned out to be another bug exposed by this fix where HTTP/1.1 CONNECT requests with authentication were filtering out proxy authentication headers wrongly. This was because the HttpRequestImpl created for the repeated CONNECT was putting the system headers in the user headers area of the HttpRequestImpl. The fix for that is to supply the user and system headers direct to the place where the new HttpRequestImpl is created.
Thanks
Michael
Progress
Issue
Reviewers
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/2977/head:pull/2977
$ git checkout pull/2977
To update a local copy of the PR:
$ git checkout pull/2977
$ git pull https://git.openjdk.java.net/jdk pull/2977/head