aws / aws/serverless-java-container

Getting 302 Found when i invoke from alb but from api gateway its returning response properly

Open
#423 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.6k
Forks
574
PR merge metrics
No merged PRs in 30d

Description

*To help us debug your issue fill in the basic information below using the options provided*

*Serverless Java Container version*: `1.6`

*Implementations:* `Spring Boot 2`

*Framework version:* `SpringBoot 2.2.1.RELEASE`

*Frontend service:* `ALB`

*Deployment method:* `Console`

## Scenario
currently spring boot app running in eks need to to deploy to lambda as containeter, image, the image is deployed suceessfully, when i invoke from api gateway test console, getting exepected results, but when i configure alb and lambda as the target, getting 302 Found, using custom doamin name

## Expected behavior
It has to return the same response how api gateway returns

## Actual behavior
302 Found

## Steps to reproduce
as its official can't provide

## Full log output
2021-08-30 10:28:58.413 INFO 6 --- [ main] c.a.s.p.internal.LambdaContainerHandler : 127.0.0.1 null- null [30/08/2021:10:28:58Z] "POST /dataloader/xxx/start/job null" 302 - "-" "PostmanRuntime/7.28.4" combined

Server: awselb/2.0
Date: Mon, 30 Aug 2021 10:28:58 GMT
Content-Type: application/octet-stream
Content-Length: 0
Location: https://xxxx/dataloader/xxx/start/job?synchronous=true
Connection: keep-alive
```
logs
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.