-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Overwriting read-only Lambda@Edge headers #262
Labels
Comments
jordaneremieff
added
help wanted
Extra attention is needed
improvement
Improve an existing feature
labels
May 10, 2022
Thanks @UnderSampled for the report and example workaround. I won't be able to look into it myself at this time, but I would be willing to review and merge any PRs to address these rules in the handler itself. |
Duplicate of: #143 |
Including handler = Mangum(
app,
# Content-Length header is not allowed in Lambda@Edge responses.
exclude_headers=["Content-Length"],
)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hooking up a Mangum lambda to CloudFront as
EventType: origin-request
returns a 502 response: "The Lambda function result failed validation: The function tried to add, delete, or change a read-only header."According to the documentation, the
Content-Length
Header is one of the read-only headers fororigin-request
events. Not quite sure why. But it's certainly one of the headers returned when calling the lambda. I use the lambda to handle API requests, so it needsIncludeBody
, which is only available with origin-request.I was able to get around this by hijacking the response:
The text was updated successfully, but these errors were encountered: