Fix static resource loading in ChannelFinder WebUI #169
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
|
I have a feeling those test failures are due to a github change in docker engine version :( |
Update relative paths for static resources in index.html to ensure proper loading when accessed under a custom context path. Previously, absolute paths caused 404 errors when the service was deployed with a non-root context path. Signed-off-by: Mariana González Velarde <[email protected]>
mgonzal1
force-pushed
the
fix-static-resource
branch
from
df2df4f to
8d8414a
Compare
|
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.
Update relative paths for static resources in index.html to ensure proper loading when accessed under a custom context path. Previously, absolute paths caused 404 errors when the service was deployed with a non-root context path.
Example:
https://services.com/channel-finder/