haproxy

History

Willy Tarreau 3f49b30284 [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-11 00:29:26 +02:00
..
400.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
403.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
408.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
500.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
502.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
503.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
504.http	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00
README	[MEDIUM] errorfile: use a local file to feed error messages	2007-06-11 00:29:26 +02:00

README

These files are default error files that can be customized
if necessary. They are complete HTTP responses, so that
everything is possible, including using redirects or setting
special headers.

They can be used with the 'errorfile' keyword like this :

    errorfile 503 /etc/haproxy/errors/503.http