aws / aws/serverless-java-container
Getting 302 Found when i invoke from alb but from api gateway its returning response properly
- 主要语言
- Java
- 星标
- 1.6k
- 派生
- 574
- PR 合并指标
- 30 天内没有已合并 PR
描述
*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
```
贡献指南
调研方向
Start by comparing the API Gateway and ALB configurations for the Spring Boot 2.2.1 application described in the issue, focusing on the logged POST request and its 302 Location response. The issue does not name source files or tests and cannot provide reproduction steps; done means identifying why ALB returns the redirect and making it return the same response as API Gateway.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- aws, java, spring-boot
- 领域
- api, backend, cloud
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100