-
-
Notifications
You must be signed in to change notification settings - Fork 501
fix head request handler again #1524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+2
−10
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add null check before calling
getResponseLength()to prevent potential runtime errors.The static route HEAD handling wraps the handler result in
Promise.resolve()and immediately chains togetResponseLength(_ht)without checking if_htis null/undefined. In contrast, the dynamic route HEAD handling (line 2298) includes anif(_res)guard before proceeding. Ifcomposed(c)returns null/undefined, this will pass null togetResponseLength(), likely causing a runtime error.Additionally, the inconsistency between static and dynamic route handling patterns makes the codebase harder to maintain.
Consider applying this pattern to match the dynamic route handling:
switchMap += `case 'HEAD':` + - `return Promise.resolve(ht[${methods.GET ?? methods.ALL}].composed(c)).then(_ht=>getResponseLength(_ht).then((length)=>{` + + `return Promise.resolve(ht[${methods.GET ?? methods.ALL}].composed(c)).then(_ht=>{` + + `if(!_ht)return\n` + + `return getResponseLength(_ht).then((length)=>{` + `_ht.headers.set('content-length', length)\n` + `return new Response(null,{status:_ht.status,statusText:_ht.statusText,headers:_ht.headers})\n` + - `}))\n` + `})})\n`Alternatively, if handlers are guaranteed to never return null/undefined, document this assumption clearly.
📝 Committable suggestion
🤖 Prompt for AI Agents