fix: fix trailing slash issues causing 404 #242
Merged
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
greghuels
force-pushed
the
greg/FF-4129/trailing-slash
branch
2 times, most recently
from
bd3a6b6 to
a1df31c
Compare
aarsilv
approved these changes
Mar 12, 2025
greghuels
force-pushed
the
greg/FF-4129/trailing-slash
branch
from
a1df31c to
ff8f385
Compare
greghuels
force-pushed
the
greg/FF-4129/trailing-slash
branch
from
ff8f385 to
8958a2d
Compare
This was referenced Mar 12, 2025
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.
Fixes: FF-4129
Motivation and Context
Some versions of React Native were experiencing 404 responses due to the JS runtime interpretation of URL.toString(). In those instances, a trailing slash was added to the path.
Description
Removed trailing slash from pathname