Fix for lambda streaming on empty body #443
Merged
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.
This PR add an env variable
OPEN_NEXT_FORCE_NON_EMPTY_RESPONSE
, when set to true it will force writing something to the stream.This should only be used with lambda streaming AND if you have issues with the stream hanging on empty body response (i.e. HEAD request, redirect...). See this discord thread
You should avoid using this as much as you can, because it modifies the response you send ( It might break some very specific cases )
It is disabled by default.