-
Notifications
You must be signed in to change notification settings - Fork 5.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
8328638: Fallback option for POST-only OCSP requests #18408
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 17 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 |
Webrevs
|
Thanks for doing this - I think it is a fine idea to have a fallback option to use POST. It does need a CSR though since you are introducing a new system property. |
/csr |
@seanjmullan has indicated that a compatibility and specification (CSR) request is needed for this pull request. @shipilev please create a CSR request for issue JDK-8328638 with the correct fix version. This pull request cannot be integrated until the CSR request is approved. |
Ideally, we should also modify the tests in
This means we would be testing real OCSP responders supported by CAs in the Java Root Program, and not just a test responder that we created. @rhalade would this change be ok with you? |
All right, good! How do you feel about the option name? Would like to arrive to consensus for it before I plaster it all over CSR text and tests. |
Yes, I am fine with the name. |
I amended the |
@shipilev this pull request can not be integrated into git checkout JDK-8328638-ocsp-post
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
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.
Looks good. Please also write a release note and I will review it.
Here you go: https://bugs.openjdk.org/browse/JDK-8329111 |
test/jdk/security/infra/java/security/cert/CertPathValidator/certification/CAInterop.java
Show resolved
Hide resolved
CSR is done. I assume we are good here, and we can integrate? |
Yes. |
All right, thanks! Here it goes. /integrate |
Going to push as commit 614db2e.
Your commit was automatically rebased without conflicts. |
See the rationale/discussion in the bug. This patch introduces the option that allows to restore pre-JDK-8179503 behavior. The default behavior does not change. Better suggestions for flag name are welcome.
Additional testing:
jdk_security
passes out of the box (includes new test config)jdk_security
passes with flag overrideGetPostTests
amended debugging output,GET
-s are used by default for small requests,POST
-s are used for everything with flag overrideProgress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18408/head:pull/18408
$ git checkout pull/18408
Update a local copy of the PR:
$ git checkout pull/18408
$ git pull https://git.openjdk.org/jdk.git pull/18408/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18408
View PR using the GUI difftool:
$ git pr show -t 18408
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18408.diff
Webrev
Link to Webrev Comment