AMQ-9739: Removed "upgrade-insecure-requests" from the Web Console's Content-Security-Policy header #1472
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Content-Security-Policy header. Fixes issues loading assets when serving the Web Console via HTTP.
sergio-d-lemos
changed the title
jbonofre
approved these changes
Aug 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes an issue unintentionally introduced by a previous commit where I added the Content-Security-Policy HTTP header to the Web Console application. The "upgrade-insecure-requests" tells the browser to automatically upgrade HTTP requests to HTTPS, which ends up breaking the assets loading in some browsers when running the Web Console with HTTP only.
I tested by browsing all the Web Console tabs in Chrome and Safari.