11–20 of 25 posts
So this is why our API had a rash of 500 errors last night. We haven't been very happy with the uptime of this service, mostly because they do deploys that break things for a couple minutes about once a month.
I wish they'd focus on speed and rebuilding API Gateway to be easier to use, or provided a new proxy option to run Lambda under. This set of changes doesn't seem to improve on any of the practical issues in using Lambda with API Gateway.
* 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 like the service and I use it for mock endpoints and other non-production applications, but I never managed to make gzip compression work in API Gateway. Actually, it seems to me that even when the origin serves gzipped content, it comes out uncompressed from API Gateway. Clearly a no-go for mobile apps. Anyone had the same experience, or did I miss something obiouvs?
API Gateway can't serve binary content, making it useless for anything but JSON toys.
I wish they'd focus on speed and rebuilding API Gateway to be easier to use, or provided a new proxy option to run Lambda under. This set of changes doesn't seem to improve on any of the practical issues in using Lambda with API Gateway.
I wish they'd focus on implementing basic HTTP support . * 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 narr…
Earlier quoted context omitted.
API Gateway can't serve binary content, making it useless for anything but JSON toys.
I don't see the value in compressing small payloads less than 1K. Plenty of APIs serve small, structured content.
(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.)
Earlier quoted context omitted.
I wish they'd focus on implementing basic HTTP support . * 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 narr…
I use a custom authorizer with Auth0 and it works fine. I guess some systems still use Basic Auth though.
I wish they'd focus on speed and rebuilding API Gateway to be easier to use, or provided a new proxy option to run Lambda under. This set of changes doesn't seem to improve on any of the practical issues in using Lambda with API Gateway.
I wish they'd focus on implementing basic HTTP support . * 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 narr…
I hope they hook up the new ALB service as an option for a Lambda proxy.
Earlier quoted context omitted.
I wish they'd focus on implementing basic HTTP support . * 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 narr…
I agree, especially regarding the documentation. I was trying not to be too negative, but using Lambda is an exercise in frustration because of API Gateway. I hope they hook up the new ALB service as an option for a Lambda proxy.
So this is why our API had a rash of 500 errors last night. We haven't been very happy with the uptime of this service, mostly because they do deploys that break things for a couple minutes about once a month.
API Gateway was a pain to use when it first came out. The API wasn't supported by AWS CLI and there were no good wrappers for it in Node.js (my preferred language for APIs). Has the situation improved?