haproxy/examples/errorfiles/500.http

HTTP/1.0 500 Internal Server Error
Cache-Control: no-cache
Connection: close
Content-Type: text/html

<html><body><h1>500 Internal Server Error</h1>
An internal server error occurred.
</body></html>
MINOR: Use "500 Internal Server Error" for 500 error/status code message. Internal Server Error is what is in RFC 2616/7231. 2017-01-09 07:17:10 -05:00			`HTTP/1.0 500 Internal Server Error`
[MEDIUM] errorfile: use a local file to feed error messages It is now possible to read error messages from local files, using the 'errorfile' keyword. Those files are read during parsing, so there's no I/O involved. They make it possible to return custom error messages with custom status and headers. 2007-06-10 18:29:26 -04:00			`Cache-Control: no-cache`
			`Connection: close`
			`Content-Type: text/html`

MINOR: Use "500 Internal Server Error" for 500 error/status code message. Internal Server Error is what is in RFC 2616/7231. 2017-01-09 07:17:10 -05:00			`<html><body><h1>500 Internal Server Error</h1>`
MINOR: fix typos in the examples files To be more specific the error 500 example page and the transparent_proxy.cfg page. For the later, it is all in the comments but still user-visible as those are examples. 2018-11-13 23:01:24 -05:00			`An internal server error occurred.`
[MEDIUM] errorfile: use a local file to feed error messages It is now possible to read error messages from local files, using the 'errorfile' keyword. Those files are read during parsing, so there's no I/O involved. They make it possible to return custom error messages with custom status and headers. 2007-06-10 18:29:26 -04:00			`</body></html>`