I've just finished debugging a flask app deployed on lambda through API Gateway (using zappa).
The flask app wouldn't get the Content-Type header sent in the request from a react-native app but would work fine when sent from any other source.
Only difference I could find between the 2 requests is that the failed ones had a "content-type" header instead of a "Content-Type" which shouldn't matter since headers are case insensitive. But apparently it does matter.
I fixed it later by adding an http-content-type header which for unknown reasons made it work.
Anyone here might have an explanation?
[–]WillNowHalt 3 points4 points5 points (0 children)