aws / aws/serverless-java-container

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

未關閉
#423 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
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
```

貢獻指南

開啟貢獻指南

研究方向

先比較 issue 中所描述之 Spring Boot 2.2.1 應用程式的 API Gateway 與 ALB 設定,著重於記錄下來的 POST 請求及其 302 Location 回應。該 issue 未指出原始檔案或測試,也無法提供重現步驟;完成的標準是找出 ALB 回傳重新導向的原因,並讓它回傳與 API Gateway 相同的回應。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
aws, java, spring-boot
領域
api, backend, cloud
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。