-
Notifications
You must be signed in to change notification settings - Fork 225
8179502: Enhance OCSP, CRL and Certificate Fetch Timeouts #2747
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 abakhtin! A progress list of the required criteria for merging this PR into |
@alexeybakhtin 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 466 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. |
At least one of the issues associated with this backport has a resolved CSR for a different version. As this means that this backport may also need a CSR, the |
Webrevs
|
CSR JDK-8337407 for JDK17 is created |
@alexeybakhtin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Hi @alexeybakhtin Thanks. |
Hi @HempushpaSahu. Yes, I will request integration into 17u as soon as it is reviewed here. |
Hi @alexeybakhtin, Thanks. |
Hello everyone, |
Hi, Thanks. |
Hi, Thanks. |
Hi @jnimeh , Thanks. |
Hello @HempushpaSahu. I can review the CSR. I think you need someone who has reviewer status in the jdk-updates project in order to be able to commit this. I only have committer status there. You should be able to find many folks with jdk-updates reviewer status on the OpenJDK census page though. |
I would also suggest looking at incorporating JDK-8309740 and JDK-8309754 in follow-on integrations as they pertain to the tests in this PR. |
Hi @seanjmullan , |
Thanks @jnimeh for your inputs. |
Hi @GoeLin |
Hi @GoeLin |
Hi @alexeybakhtin, Thanks. |
CSR is approved. |
Hi @alexeybakhtin , I have tested the four backports mentioned above together, and they have passed successfully. Should we include these tests as part of the PR? |
@franferrax , @HempushpaSahu, Thank you!
Backports are clean, so no review is required |
Hi @alexeybakhtin, thank you for the additional time and effort put into this! My intention is to help move things faster, because I've been made aware about customers waiting for this. However, as @GoeLin explained, if Oracle doesn't include this backport in 17.0.14, the documentation won't be updated, so we'll need to wait for them to proceed. Apparently, Oracle's reason for not doing the backport is its low priority. Customers are now trying to get it prioritized through Oracle support, but it looks like we won't make it for the 17.0.14 rampdown date (December 3). NOTE: FYI, AFAIK, you can add multiple backports to a pull requiest with the |
Hi @franferrax, About |
@alexeybakhtin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
/csr 8337407 |
@alexeybakhtin usage: |
@alexeybakhtin: looks like linking the right CSR (JDK-8337407) from the Oracle backport (JDK-8338808) did the trick. Also, I think "parity with Oracle" is now a valid reason for maintainer approval, since jdk17u-dev is in the development phase of 17.0.15, the same version for which Oracle did the backport. |
This change looks good to me now. Thanks for improving the compatibility with 17! |
+1 on bringing this to JDK 17 in April. There is ample time until that releases. |
Oracle just integrated the fix for the upcoming April release: https://bugs.openjdk.org/browse/JDK-8338808?focusedId=14737263&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14737263 |
/integrate |
Going to push as commit 25c7a7b.
Your commit was automatically rebased without conflicts. |
@alexeybakhtin Pushed as commit 25c7a7b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hello, I'd like to backport JDK-8179502 to JDK17u to improve the timeout adjustment for OCSP GET requests (which was missed in JDK-8179503).
The backport is almost clean except for the following:
All new and related jtreg tests are passed
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2747/head:pull/2747
$ git checkout pull/2747
Update a local copy of the PR:
$ git checkout pull/2747
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2747/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2747
View PR using the GUI difftool:
$ git pr show -t 2747
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2747.diff
Using Webrev
Link to Webrev Comment