Skip to content

Conversation

@lachlan-roberts
Copy link
Contributor

Closes #29552

The list returned from context.getAliasChecks() is not designed to be mutated directly. In later versions of Jetty (10+) this has become an unmodifiable list.

This PR changes the usage to instead use the context.clearAliasChecks() method which also manages the LifeCycle of the alias checker.

…from Jetty WebAppContext

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@pivotal-cla
Copy link

@lachlan-roberts Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 25, 2022
@pivotal-cla
Copy link

@lachlan-roberts Thank you for signing the Contributor License Agreement!

@bclozel bclozel added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 25, 2022
@bclozel bclozel added this to the 2.5.10 milestone Jan 25, 2022
@bclozel bclozel changed the title Issue #29552 - don't modify AliasChecks list directly from Jetty WebAppContext Don't modify AliasChecks list from Jetty WebAppContext Jan 25, 2022
@bclozel bclozel closed this in f1bbce1 Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: task A general task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Do not use Jetty WebAppContext#getAliasChecks() to clear collections but use clearAliasChecks()

4 participants