4 ms·
who memorizes http response codes?
by lj3 10y ago
who memorizes http response codes?
- ep103 10y agoWho can't tell the difference between a 404 and a 500?
- falsedan 10y agoSomebody who rarely instructs a user agent to make requests to a server.
- 6nf 10y agoThe people in question do in fact use internet browsers on a daily basis.
- falsedan 10y agoThat's good to hear.
- RandomOpinion 10y agoSo, basically, somebody who never uses a web browser? 404 and 500 should be familiar just from browsing the web for more than a few weeks.
- dragonwriter 10y agoModern browsers seem to do quite a bit to insulate users from error status codes in their default configurations.
- badthingfactory 10y agoThis isn't entirely accurate. I told my RN Fiance this story and she said "oh 404, that's like... page not found or something isn't it?" She has zero programming experience.
- jcadam 10y agoProgrammers who want their REST API to return correct http response codes. I have a good many of them memorized by now. :( ...someday I'll find an excuse to return a 418.
- lj3 10y agoBah! Just always return 200 and if there's an error, make your users look for an error property in the json return value that contains a thoroughly unhelpful error message, like "I'm a teapot." ;)
- deleted 10y ago[deleted]
- dragonwriter 10y agoPresumably, programmers who are working with the web should have a passing familiarity with the most common categories; this isn't memorizing all of them, but being able to recognize the significance of 2xx vs 3xx vs 4xx vs 5xx codes isn't an unreasonable expectation.