4 ms·
> Turns out, they use SIGWINCH (which is sent on WINdow CHange) for graceful shutdown. That’s … that’s even worse than people who send errors with an HTTP 200
by eadmund 2y ago
> Turns out, they use SIGWINCH (which is sent on WINdow CHange) for graceful shutdown.
That’s … that’s even worse than people who send errors with an HTTP 200 response code.
- chrsig 2y agoy'know...what really is an error, anyway?
- thebruce87m 2y agoFor what is an error, if not a success at failing?
- chrsig 2y agoExactly. Gotta be happy you got a response at all!
- AStonesThrow 2y agoIn my day, successful commands output nothing at all, so it would seem that a blank page is the only truly error-free result.
- aunderscored 2y agoDisagree. Annoyingly there is a reasonable case for 200 but with an error, if http is your transport but not your application, then 200 says "yes, the message was transfered and understood correctly, here is your response" which may be an error response from the application
- Izkata 2y agoFor example: Apache (httpd) replaces the 4xx and 5xx response body with its own content instead of whatever you'd returned from an external handler like wsgi. You have to use a 2xx (except for 204) to get a relevant error message back out.
- AdieuToLogic 2y ago> For example: Apache (httpd) replaces the 4xx and 5xx response body with its own content instead of whatever you'd returned from an external handler like wsgi. This is the default behavior. Apache httpd can be configured to produce different responses by way of ErrorDocument[0]. From the documentation: Customized error responses can be defined for any HTTP status code designated as an error condition - that is, any 4xx or 5xx status. HTH 0 - https://httpd.apache.org/docs/trunk/custom-error.html https://httpd.apache.org/docs/trunk/custom-error.html
- jjnoakes 2y agoEven with custom error documents configured in the web server, you still lose the application-specific (and probably request- and error-specific) message generated by the application itself.
- Izkata 2y agoYeah, this is how we ran across it - whoever originally wrote a particular feature was trying to do the right thing by using an HTTP error code, but with a message that would be presented to the user about why that operation failed. A generic response wouldn't work, there were multiple possible reasons all fixable by the user, and tying a whole error code to one specific feature would've probably been a bad idea anyway.
- Groxx 2y agoWhich is why "you resized the terminal window, clearly you meant to shut down this web server" is even crazier, yes
- aunderscored 2y agoIndeed. That is particularly good at violating the principle of least astonishment
- eadmund 2y agoIf you’re using HTTP for something other than transferring hypertext — i.e., if your application is not a hypermedia application — then you are doing something just as wrong as encoding IP in DNS packets or email messages. Don’t do that. It’s wrong, even if it is technically interesting. If, OTOH, your application is a hypermedia application, then returning a success status for errors is just wrong.
- aunderscored 2y agoEvery JSON API under the sun disagrees, but I do agree in principle. People very much like using HTTP as a JSON (or XML) transfer protocol
- andreyvit 2y agoSorry, what? HTTP is perfectly fine for APIs which are not hypermedia.
- sunshowers 2y agoThis ship sailed the day the first HTTP proxy was installed, and likely well before that.
- thezilch 2y agoThat's ... not what most people are doing. People send _application_ errors on HTTP 200 response codes, because HTTP response codes are for HTTP and not applications. Most "REST" libraries and webdev get this wrong, building ever more fragile web services.
- ChocolateGod 2y agoApplications using status codes is useful because it can tell browsers and load balancers to not cache the page in a uniform way.
- LoganDark 2y agoTask failed successfully
- sunshowers 2y agoI don't think the distinction is as clear-cut as you're making it out to be. For example, HTTP 409 Conflict generally means an application-level conflict (e.g. an optimistic concurrency mechanism detected a conflict). HTTP 422 Unprocessable Entity is also usually an application-level error (e.g. hash validation failure, or identifier not recognized by the server).