- Newest
- Most votes
- Most comments
Header names are converted to lower case, so apigw-clientapp and APIGW-ClientApp appear to be the same header when they are both present, then based on order the last one wins and is passed through. This is the case for a header set with both apigw-clientapp and APIGW-ClientApp which isn't a real world example.
From my testing any lower case header starting with apigw- will not get passed.
The list of API Gateway Reserved Headers contains this header name: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-parameter-mapping.html#http-api-mapping-reserved-headers
I recommend selecting a different header name.
Hi, this article will help in customizing the headers that you need to pass to your Lambda: https://repost.aws/knowledge-center/custom-headers-api-gateway-lambda
It goes quite far in all details to configure properly.
The link you have provided is for REST API. I want to achieve the same in HTTP API and there is problem in forwarding this apigw-clientapp header
Relevant content
- asked 2 years ago
- Accepted Answerasked 9 months ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
Even if I send apigw-clientapp header alone to api gateway(HTTP_API with HTTP_PROXY), it doesn't pass to lambda.