2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
The list of API Gateway Reserved Headers contains apigw-
: 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.
con risposta un anno fa
0
Hi,
This seems to have been a problem already in the past: see https://github.com/aws/aws-lambda-dotnet/issues/915 But ticket is closed probably because according to documentation
Header names and query parameters are processed in a case-sensitive way.
See https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-known-issues.html and check the full table on this page for all standard parameters
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- Perché ricevo un errore HTTP 403 Forbidden quando mi connetto alle mie API di API Gateway da un VPC?AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Thanks. Is there something with prefix apigw? because it works for any lowercase headers but particularly not the headers that has prefix apigw