Beyond Ctrl-C: The dark corners of Unix signal handling

Re:Beyond Ctrl-C: The dark corners of Unix signal handling by AdieuToLogic on Sunday September 08, 2024 @08:00AM (#41479902)

> 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

[ Parent | on HN ]

Re:Beyond Ctrl-C: The dark corners of Unix signal handling by jjnoakes on Sunday September 08, 2024 @01:41PM (#41481816)

Even 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.

[ Parent | on HN ]

Re:Beyond Ctrl-C: The dark corners of Unix signal handling by Izkata on Sunday September 08, 2024 @02:39PM (#41482190)

Yeah, 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.

[ Parent | on HN ]