-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8367976: Validate and clamp jdk.httpclient.bufsize #27874
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 vyazici! A progress list of the required criteria for merging this PR into |
|
@vy 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 26 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
|
|
You will also need to update module-info.java where the property is documented, to indicate what is the range of valid values and what happens if an invalid value is provided. |
Implemented in 148d426. I presume this warrants a CSR, right? |
|
It's an implementation specific property - so not part of the Java SE specification. IMO it was a bug that we didn't clamp it in the first place. There's no real change in observable behaviour here. I am not sure we actually need a CSR. |
Co-authored-by: Daniel Fuchs <[email protected]>
|
@vy Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
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.
LGTM
|
@dfuch, thanks so much for the review feedback – it, as always, certainly helped. Tier 1-2 is clear on several platforms. /integrate |
|
Going to push as commit cbbb0a8.
Your commit was automatically rebased without conflicts. |
Validate and clamp the value populated from the
jdk.httpclient.bufsizesystem property. Added two new tests: Does clamping work? Does the minimum value wedge the client?Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27874/head:pull/27874$ git checkout pull/27874Update a local copy of the PR:
$ git checkout pull/27874$ git pull https://git.openjdk.org/jdk.git pull/27874/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27874View PR using the GUI difftool:
$ git pr show -t 27874Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27874.diff
Using Webrev
Link to Webrev Comment