3 ms·
This is kind of unfortunate because if they just returned a correct code (429 Too Many Requests), you could have immediately debugged the problem. (The standar
by jrockway 6y ago
This is kind of unfortunate because if they just returned a correct code (429 Too Many Requests), you could have immediately debugged the problem. (The standard suggests also including a Retry-After header, which would tell you when the rate limiting would be lifted so you could try again.)
Basically, there was a machine-readable way to tell you to go away. But instead they told your user agent that they were unable to brew coffee because they are a teapot. What a waste of everyone's time.
- csilverman 6y agoAgreed, although the iOS Shortcuts app did not even bother to tell me the server's response; it simply failed, so even if the server had returned a coherent error message, I think I still would have had to contact support to find out what it said. I love Shortcuts—it's a great automation tool with some good ideas—but, as is the case with many Apple things, it prioritizes minimalism over functionality. Seems like an odd tradeoff to me, since I think the only people who even know Shortcuts is on their device are people like me who would vastly prefer full-featured complexity—and better documentation—to the smooth, almost toy-like UX.