3 ms·
The Uber Eats glitch that allowed ordering free food for a weekend in India
- asfarley 5y agoThe description talks about idempotency to make it seem complicated, but really this sounds like they just didn’t check for an explicit OK response and instead decided to blacklist only certain error codes from the API. Sounds like a sloppy decision on Uber Eats part to me.
- Arnt 5y agohttps://nitter.net/GergelyOrosz/status/1502957116776198144#m https://nitter.net/GergelyOrosz/status/1502957116776198144#m describes the second response as a "status that is not an error (also not success)" so it was quite clearly not a matter of an error with an unhandled error code. Another tweet also says explicitly that they handled all errors that were defined when the code was written. Tricky.
- upbeat_general 5y agoAs long as the API provider specified what a “success” response looks like, the fault goes to the API consumer. I also find it crazy that anyone would consider failing open for a payment API like this, at least not without a lot of forethought and oversight. Failing open can make sense in some cases but even for a company heavily focused on growth…it seems like a horrible idea.