This repository has been archived by the owner on Jan 30, 2023. It is now read-only.
Fix inconsistency in authentication path prefix to remove trailing slash #29
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.
WHY are these changes introduced?
There are inconsistent assumptions around whether the authentication middleware should use a trailing slash in the prefix. The
createShopifyAuth
function assumes no trailing slash, butrequestStorageAccess
assumes trailing slash. This leads to a 404 error whenrequestStorageAccess
attempts to access a url in the form:customprefixauth/inline?shop=
. Note the missing slash betweencustomprefix
andauth/
.WHAT is this pull request doing?
Update the
requestStorageAccess
function to assume no trailing slash in the prefix.Type of change
Checklist