-
Notifications
You must be signed in to change notification settings - Fork 560
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
SpringDelegatingLambdaContainerHandler does not handle Headers correctly for FunctionUrls #860
Comments
@olegz I found some more problems 😉 |
For the record after making the required changes to the |
Why do you use |
I use a function URL instead of a full API GW as "frontend" for the lambda. As per the docs they should both use the exact same request and response payload schema. I wonder why the |
I see |
Ok this is weird. Maybe it is a bug with AWS function urls. I will try to reproduce it next week. |
I just ran into the rewriting of the headers to lowercase.
I'm using Jersey. |
Serverless Java Container version:
com.amazonaws.serverless:aws-serverless-java-container-springboot3:2.1.0-SNAPSHOT
Implementations:
Spring Boot 3
Framework version:
SpringBoot 3.2.5
Frontend service:
FunctionUrl
Deployment method:
SAM
Scenario
I still try to render freemarker templates via a spring boot lambda. I want to serve those lambdas via a FunctionUrl for simplicity reasons
Expected behavior
When calling the path where the template is rendered, the response should contain the correct template with the correct headers.
Actual behavior
For API GW Requests this works as expected. For FunctionUrl requests it does omit at least the
content-type
header and always replaces it withapplication/json
Steps to reproduce
sam build && sam deploy --guided
in this modified sample for alt-pet-storeFull log output
FunctionUrl
Cloudwatch:
curl (note the
Content-Type
header)Api GW
This is working as expected
The text was updated successfully, but these errors were encountered: