Correct Top URL #29
Merged
Correct Top URL #29
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
bjornaer
previously approved these changes
Jan 24, 2022
alexpearce
force-pushed
the
apearce-top-url
branch
from
4618b48 to
f6bc1ec
Compare
bjornaer
previously approved these changes
Jan 31, 2022
alexpearce
force-pushed
the
apearce-top-url
branch
from
f6bc1ec to
5d1474c
Compare
bjornaer
approved these changes
Jan 31, 2022
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.
The trailing slash results in a redirect response, but the redirect doesn't include the
Authorizationheader in production so causes 403 errors.(Most Top URLs do not end in a slash;
POST /v2/files/is one exception I know of, there may be others)