ErrorFile Content-Type

[nagyrobi]

Apparently the files specified in ErrorFile directives use "Content-Type: text/html", I guess because most people would use HTML files for them. I think it would be appropriate to have an option to change from this default, specifically I'd find useful to be able to serve these with "Content-Type: text/plain" header.

[graygnuorg]

Hi Róbert.
That sounds reasonable. I thought, however, that instead of introducing one more configuration statement, it would be more convenient to let the admin supply any headers they seem fit in the error file itself. This is implemented in commit af9e878. To mark your error file as plaintext, start the file with Content-Type: text/plain, followed by an empty line. You'll find more details on error file handling here: https://www.gnu.org.ua/software/pound/manual/Error-responses.html

[graygnuorg]

Do I get it right, that "replacing" means that the status code would remain unchanged, and only the content of the response would be changed?

[nagyrobi]

Exactly.
So you can have a centrally managed place for status code pages of all the backends.

[graygnuorg]

It is implemented in commit cbac9bc. The feature is documented here: https://www.gnu.org.ua/software/pound/manual/Error-response-rewriting.html. Any feedback is much appreciated.

[graygnuorg]

Update: I've forgotten about 4xx codes. The commit 876b39c fixes that.

[nagyrobi]

Thank you. It works nicely.