I am using an AWS proxy ApiGateway that is mapped to a lambda function that is hosting a REST Api. Everything is wired up and functioning, except I see that responses from the server are remapping my 'Authorization' header to 'x-amzn-remapped-authorization', which is causing problems for web clients that are looking for the 'Authorization' key in the response headers.
I picked a proxy integration setup because I don't want Amazon to do anything special, just serve requests. I realize that I could tell the clients to read the remapped key, but that is bending to accomidate Amazon's 'decision'. I think I have correctly set CORS to properly expose the Authorization header, and I have the 'Lambda proxy integration' option turned on in the Api gateway. Is something I am missing to disable this remapping?
Authorizationis a request header, you shouldn't have it in your responses anyway?Authorizationheaders on requests, yes. On responses, no.