Lissy93/web-check

[Bug] X-Forwarded-Port header causes Internal Server Error

Opened this issue · 1 comments

I run Web-Check behind a Traefik proxy. Since the latest container release it's been throwing a 500 on any/all requests, even favicons. I figured I'd wait a while to see if it was something missed in development but I figured today I'd take a crack at it:

Traefik automatically supplies some headers for forwarded requests, particularly X-Forwarded-Port in this case. Web-Check will always return a 500 if that header exists in a request. I removed the header for now and it's fine:

- 'traefik.http.middlewares.web-check_bug-fix.headers.customrequestheaders.X-Forwarded-Port='

I forgot to add - and this should be rather helpful - this did not happen in the 1.0.0 Docker image.