Skip to content

[#2659] Send web console security headers from the server handler chain - #2874

Open
SAY-5 wants to merge 1 commit into
apache:mainfrom
SAY-5:fix-2659-security-headers
Open

SAY-5 wants to merge 1 commit into
apache:mainfrom
SAY-5:fix-2659-security-headers

Conversation

@SAY-5

@SAY-5 SAY-5 commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Fixes #2659.

The RewriteHandler was added to the Contexts collection as a sibling of the webapps, so none of its header rules ran; it is now inserted at the Server level like the other wrappers, in both the shipped and the test jetty-webapps.xml. With the CSP now actually sent, the three inline onclick confirms in browse.jsp and message.jsp would be blocked, so they move to js/browse.js and js/message.js as the review on #2676 asked. JettyServerBeanTest now logs in through a test PropertiesLoginModule config and checks for a 200 carrying X-Frame-Options (it fails without the XML change).

…er chain

Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
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.

Web console security headers are not sent (RewriteHandler in jetty-webapps.xml never wraps the webapps)

1 participant