Have you tried to add the $RESPONSE_CODE macro into your err.html file? It would help to figure out which response code httpd is actually sending.
On 2023-09-14 11:00, Stephan Thomann wrote: > 1. The first question is related to httpd and handling of error pages (http > errors). I created a directory "errdocs" underneath /var/www and put in > several documents, among them 403.html, 404.html, err.html. > > I updated /etc/httpd.conf accordingly (first in the global section, then in > the server sections, no difference). A "404" on the top level sends me the > 404.html file as expected. Example: "<mydomain>/gaga.html". Same for > "<mydomain>gaga", so it seems independent of mime type or file extentsion. > But as soon as the path contains a "/", the file "err.html" is used instead, > so I get the rendered "err.html" when I request "<mydomain>/gaga/" instead of > "<mydomain>/gaga". This seems a bit unexpected to me but could be intended > behaviour. I can live with that, but wanted to understand if I made something > wrong. >
