-
Notifications
You must be signed in to change notification settings - Fork 559
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
Error with version 2.0.2 when multi-value header is active in alb #909
Comments
@LennardWolf2023 a fix has been merged to 2.0.x and main branch. Can you please validate it using a SNAPSHOT build? We plan to ship a 2.0.3 release tomorrow. |
@deki thank you for the fast response. We tried to find the corresponding snapshot, but were only able to find a snapshot for archetype underneath https://aws.oss.sonatype.org/content/repositories/snapshots, but not the spring boot3 version. Do you have a link, where we can find the snapshot. |
We also saw, that the release 2.0.3 was initiated. When the package is available, we try it out using the release. |
Yeah I just triggered it. Should be in Maven Central soon. |
Release is there now. Please let us now if you still see any issues. |
Serverless Java Container version:
2.0.2
Implementations:
Spring Boot 3
Framework version:
SpringBoot 3.2.6.RELEASE
Frontend service:
ALB|RestController
Deployment method:
AWS Cloud Development Kit
Scenario
We tried to migrate the server less java container spring boot version we are using from version 2.0.1 to 2.0.2. We are using the framework for our lambda which is accessible by an alb, which has a certain target groups, that directs the calls to the corresponding lambda. The lambda provides a spring @RestController with Post and Get Mappings. With version 2.0.1 everything worked fine.
Expected behavior
By increasing the version in the build gradle dependencies, we wanted to migrate to the new version without any additional workaround or further action.
Actual behavior
When multi-header value (attribute on target group of lambda:
lambda.multi_value_headers.enabled
) are configured in the alb, the requests directing to lambda are answered with HTTP status code 502. The error occurs, when the lambda should be invoked by a HTTP request to its endpoints. Please see stack trace in full log output.Steps to reproduce
Create a lambda with corresponding 2.0.2 version of framework, that is invoked by an alb and target group that the user can the endpoint provided by the lambdas @RestController. The multi-value headers need to be activated at the target group level.
For the setup description in https://github.com/aws/serverless-java-container/wiki/Quick-start---Spring-Boot3 is used as template.
Full log output
The text was updated successfully, but these errors were encountered: