-
Notifications
You must be signed in to change notification settings - Fork 224
8328638: Fallback option for POST-only OCSP requests #2338
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 shade! A progress list of the required criteria for merging this PR into |
@shipilev 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 23 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 |
This backport pull request has now been updated with issue from the original commit. |
665592a
to
c557047
Compare
/issue add JDK-8329213 |
@shipilev |
|
/approval 8328638 request Improves JDK OCSP compatibility with some real world OCSP responders. Starts to be a problem since JDK 17 introduced GET OCSP requests. Risk is medium-low, as default behavior is not changed, and the code is simple. Passes full jdk_security tests, eyeballed logs show the expected behavior. /approval 8329213 request Option checking followup for JDK-8328638. Risk is low, simple refactoring. Passes full jdk_security tests, eyeballed logs show the expected behavior. |
@jerboaa, @RealCLanger -- what do you think about this one? Would be nice to unblock JDK 17 for folks. |
Makes sense. /approve |
@RealCLanger usage: |
/approve yes |
@RealCLanger |
/integrate |
Going to push as commit 533fac6.
Your commit was automatically rebased without conflicts. |
Improves JDK OCSP compatibility with some real world OCSP responders. Starts to be a problem since JDK 17 introduced GET OCSP requests. The default behavior is not changed.
The backports are almost clean, I just had to add the import for
Locale
andDebug
in one of the files.Locale
is added in mainline by JDK-8312443, which I do not want to backport at the moment, as it changes existing security code.Debug
is added by JDK-8179502, which is also not amenable for easy backporting.Additional testing:
jdk_security
pass, includes new test casesProgress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2338/head:pull/2338
$ git checkout pull/2338
Update a local copy of the PR:
$ git checkout pull/2338
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2338/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2338
View PR using the GUI difftool:
$ git pr show -t 2338
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2338.diff
Webrev
Link to Webrev Comment