fix: run registered HEAD handler instead of always returning default 204 - #74
Merged
Conversation
szanata
approved these changes
Aug 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
LambdaApi.process()short-circuited everyHEADrequest with a hardcoded204 <empty>, before handler matching even ran. Any handler registered withmethod: 'HEAD'was silently ignored.Fix
Move the
HEADshort-circuit inside the "no handler matched" branch. If aHEADhandler is registered, it now runs like any other verb; if none is registered, behavior is unchanged (204 <empty>).Tests
Docs
Updated
docs/lambda_api/index.mdto describe the new precedence (registered handler > default 204).