fix: check for valid content-length before calling request.formData()
for HEAD
requests
#662
+54
−3
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?
Currently the login handler will call
request.formData()
if no?shop=xxx
param was found and it's aGET
request. In RemixHEAD
requests will be handled asGET
requests, so if noshop
param was provided in aHEAD
request, e.g. by just visiting/auth/login
(using the shopify remix template), it would then call therequest.formData()
function on an empty body and throw aTypeError: Could not parse content as FormData
.WHAT is this pull request doing?
The PR enhances the current
if (request.method === 'GET' && !shopParam)
check to also check if theContent-Length
header is truthy/above zero. If so, it should be safe to callrequest.formData()
. It does not impact any other request types such asPOST
.Type of change
Checklist
yarn changeset
to create a draft changelog entry (do NOT update theCHANGELOG.md
files manually)