Skip to content

8365086: CookieStore.getURIs() and get(URI) should return an immutable List #26698

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

Closed
wants to merge 4 commits into from

Conversation

jaikiran
Copy link
Member

@jaikiran jaikiran commented Aug 8, 2025

Can I please get a review of this change which proposes to address the issue noted in https://bugs.openjdk.org/browse/JDK-8365086?

java.net.CookieStore has some APIs which return a java.util.List. These API are specified to return an immutable List. The JDK ships an implementation of the CookieStore - the java.net.InMemoryCookieStore. The implementations of the getURIs() and get(URI) methods in the InMemoryCookieStore currently return a List which is modifiable.

The changes in this PR fix those two method to return an immutable List to match the specification. A new regression test has been introduced to reproduce the issue and verify the fix.

I think this may not require a CSR since this fixes the implementation to match the already existing specification in CookieStore. I will create one if anyone suggests we should.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8365086: CookieStore.getURIs() and get(URI) should return an immutable List (Bug - P3)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26698/head:pull/26698
$ git checkout pull/26698

Update a local copy of the PR:
$ git checkout pull/26698
$ git pull https://git.openjdk.org/jdk.git pull/26698/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26698

View PR using the GUI difftool:
$ git pr show -t 26698

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26698.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 8, 2025

👋 Welcome back jpai! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 8, 2025

@jaikiran 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:

8365086: CookieStore.getURIs() and get(URI) should return an immutable List

Reviewed-by: liach, vyazici, dfuchs

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 4 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Aug 8, 2025

@jaikiran The following label will be automatically applied to this pull request:

  • net

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.

@openjdk openjdk bot added net [email protected] rfr Pull request is ready for review labels Aug 8, 2025
@mlbridge
Copy link

mlbridge bot commented Aug 8, 2025

Webrevs

* as expected
* @run junit CookieStoreTest
*/
class CookieStoreTest {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise you get a warning that the comment block should start with a /**:

Suggested change
class CookieStoreTest {
class CookieStoreTest {

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Volkan, is that warning generated by a IDE? I don't see it in IntelliJ:

ide

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we usually put the jtreg directive block before the imports.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that warning generated by a IDE? I don't see it in IntelliJ:

@jaikiran, I remember seeing it highlighted somewhere, but apparently I am mistaken. Nevermind. It is all good.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Chen,

I think we usually put the jtreg directive block before the imports.

It's a mix of before imports and above the class declaration in the JDK repo. I personally prefer just above the class since it's easily visible. Several of the tests in the networking area follow this currently.

Comment on lines 107 to 110
// the returned list is expected to be immutable, so the attempt to add or remove
// an element must fail
assertThrows(UnsupportedOperationException.class, () -> cookies.add(cookie));
assertThrows(UnsupportedOperationException.class, () -> cookies.remove(cookie));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: You can consider factoring this out to a assertCookieStoreIsImmutable(CookieStore) method.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I've moved couple of those assertions to a separate method to be called from each of these test methods.

Copy link
Member

@dfuch dfuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. It may be useful to plan a release note, in case an application is depending on being able to add/remove stuff to/from the returned list, despite the documentation stating they should be immutable. For instance - an application may attempt to clear() the returned list.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 8, 2025
* as expected
* @run junit CookieStoreTest
*/
class CookieStoreTest {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we usually put the jtreg directive block before the imports.

// the list is expected to be immutable, so the attempt to add or remove
// an element must fail
assertThrows(UnsupportedOperationException.class, () -> list.add(elementToAddOrRemove));
assertThrows(UnsupportedOperationException.class, () -> list.remove(elementToAddOrRemove));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think trying list.set would be meaningful too, given Arrays.asList would pass these two tests but is actually mutable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I've updated the PR to include that additional check.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Aug 9, 2025
Copy link
Member

@liach liach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code alone looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 9, 2025
@jaikiran
Copy link
Member Author

It may be useful to plan a release note, in case an application is depending on being able to add/remove stuff to/from the returned list, despite the documentation stating they should be immutable. For instance - an application may attempt to clear() the returned list.

I've now marked the issue with release-note=yes. I'll create one shortly.

@jaikiran
Copy link
Member Author

Thank you all for the reviews.

@jaikiran
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Aug 10, 2025

Going to push as commit 022e29a.
Since your change was applied there have been 5 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Aug 10, 2025
@openjdk openjdk bot closed this Aug 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Aug 10, 2025
@openjdk
Copy link

openjdk bot commented Aug 10, 2025

@jaikiran Pushed as commit 022e29a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@jaikiran jaikiran deleted the 8365086 branch August 10, 2025 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrated Pull request has been integrated net [email protected]
Development

Successfully merging this pull request may close these issues.

4 participants