Skip to content

Set the CORS filter credentials parameter explicitly instead of a header name the filter ignores - #8976

Merged
rzo1 merged 1 commit into
masterfrom
fix/webapp-cors-filter-defaults
Aug 22, 2026
Merged

Set the CORS filter credentials parameter explicitly instead of a header name the filter ignores#8976
rzo1 merged 1 commit into
masterfrom
fix/webapp-cors-filter-defaults

Conversation

@rzo1

@rzo1 rzo1 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

corsFilterHandle passed CrossOriginFilter.ACCESS_CONTROL_ALLOW_ORIGIN_HEADER, a response header name, where an init-param name was expected, so Jetty ignored the line and the filter ran on its own defaults.

Sets ALLOW_CREDENTIALS_PARAM explicitly and pins all four init-params in UIHelpersTest.

@rzo1 rzo1 added this to the 3.1.0 milestone Aug 19, 2026
@rzo1 rzo1 self-assigned this Aug 19, 2026

@GGraziadei GGraziadei left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hi Richard, thanks, LGTM.

GitHub flagged some methods as deprecated and marked for removal (but not on the changed lines). This is a separate issue that we can address in the future.

@rzo1
rzo1 force-pushed the fix/webapp-cors-filter-defaults branch from e4d7bd4 to e779409 Compare August 22, 2026 16:54
@rzo1
rzo1 force-pushed the fix/webapp-cors-filter-defaults branch from e779409 to ad0811d Compare August 22, 2026 17:08
@rzo1
rzo1 merged commit ed585b8 into master Aug 22, 2026
3 checks passed
@rzo1
rzo1 deleted the fix/webapp-cors-filter-defaults branch August 22, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants