Handle path prefix when serving web interface assets. (6.1)
#21219
Conversation
This file contains 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
* Handle path prefix when serving web interface assets. * Adding tests for frontend asset consistency. * Adding changelog snippet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note: This is a backport of #21104 to
6.1.Description
Motivation and Context
This PR is making sure that if a path prefix is configured through the
http_publish_uri(in contrast to through theX-Graylog-Server-URLheader), it will be considered when looking up assets.Fixes #21015.
How Has This Been Tested?
It has been tested with configuring
http_publish_uriwith and without a path prefix, with a trailing slash and without it and without the directive at all.Screenshots (if appropriate):
Types of changes
Checklist: