* you can't serve non-UTF8 content
* HEAD is totally broken (you can't set Content-Length)
* custom authorizers are useless with 3rd-party clients since you can't set WWW-Authenticate
* 100 Continue is blindly sent before checking auth
And then if they could get around to writing an actual reference document rather than the rambling stream-of-consciousness narratives they have currently, then maybe I'll be able to learn what the heck an "Integration Request" is and what syntax custom authorizers are supposed to return.
I hope they hook up the new ALB service as an option for a Lambda proxy.
Has the situation improved?
and is part of the SDK for Node: https://aws.amazon.com/sdk-for-node-js/
(Note that it's not like API Gateway claims up front "JSON only!" or some such. Outbound binary data just silently gets garbled and the only mention of this limitation is buried in various threads on the forums.)
Six months I was looking around and found that API gateways from various vendors addressed everything somebody might want in an API gateway except the one thing you need for a minimal viable product -- a way to charge for API calls.
