bug: API Gateway Proxy does not forward the backend response code (always returns 200) #10461
Closed
1 task done
Labels
aws:apigateway
Amazon API Gateway
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
The LocalStack-based API Gateway does not forward the HTTP code from the backend and instead always returns a 200 response, regardless of what the backend response code was:
Expected Behavior
According to the AWS Documentation, For proxy integrations, API Gateway automatically passes the backend response to the method response. In other words, if the backend is returning an HTTP 401, the API Gateway should also return a 401 (not 200), as confirmed when deploying the same infrastructure to AWS:
How are you starting LocalStack?
With a
docker run
commandSteps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Terraform code
Init && apply
tflocal init && tflocal apply
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: