Improve support for X-Forwarded-Path #1459
Open
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
|
Don't the other pages do this through utils.js instead of doing it themselves? I thought here was a function to create the public url. I will look later when i have some time. |
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.
X-Forwarded-Path is already supported in e.g. getTileUrls() from utils.js, but missing in other places.
This fixes the urls with X-Forwarded-Path for all templates (data.tmpl, viewer.tmpl, index.tmpl, wmts.tmpl).
This pull request adds support to the public_url from serveTemplate() function, used by data.tmpl, viewer.tmpl and index.tmpl. Additionally it adds support to baseUrl from serving wmts.xml.