alt Hacker NewsHow many times has the stable and established X surprised you with some unexpected behavior?
Once upon a time I wanted a URL /like/this/with%2Fslashes/ where a path parameter could, in rare cases, contain an encoded slash. Legit according to every RFC I checked. Works fine in browsers. But I couldn't get the web server to not convert it to a / before hitting my code. And woe betide thee who wants to make nginx return a custom error code 444.
Replies
firesteelrain • today at 1:44 AM
RFC 3986 treats %2F as a reserved character that behavior becomes app specific.
How many times have existing APIs made by experts in their fields had bugs.
How many of those are you willing to let your own services and your customers’ data be hit by whole classes of bugs that battle-hardened APIs have already fixed?
You sure you can get an LLM to handle every single one of them on first pass? Would you stake your company reputation and the PII of all your customers on it?