Closed jinnatar closed 1 year ago
Hi @Artanicus! Why did you decide this is an error? For example, traefik expect 200 code (as I remember) to serve the error page content
From my previous tests with plain nginx responders, Traefik seemed to pass the error service response code to the client as-is, which breaks monitoring as everything seems like 200
. Let me double check the repro via Traefik.
I can confirm that Traefik functions as you expected, i.e. it expects a 200
from the service but still emits the correct status to the end user. My bad!
Is there an existing issue for this?
Describe the bug
Fetching a specific error with
/403.html
(and anything not 404) returns asHTTP/1.1 200 OK
but with the correct template content. Instead fetching/
with aX-Code: 403
works as expected.Steps to reproduce
docker run --rm -it -p 1234:8080 ghcr.io/tarampampam/error-pages:2.24
curl -v -H "X-Code: 403" localhost:1234 > /dev/null
->< HTTP/1.1 403 Forbidden
curl -v localhost:1234/403.html > /dev/null
->< HTTP/1.1 200 OK
Configuration files
Relevant log output
Anything else?
No response