Traefik sends a forward auth request for every request, including HEAD methods, in order to validate if a request can continue.
Due to Go HTTP client being strict to the HTTP SPEC, the response of a HEAD does not include a body, while Traefik expects a validation response to be embedded, causing errors.
To mitigate this, when a X-Forwarded-Method is set as HEAD, we'll avoid modifying the HTTP Method response in order to send a body back, allowing head requests to by validated.
This is necessary even if an allow rule is set, otherwhise it will fail as well.
Traefik sends a forward auth request for every request, including HEAD methods, in order to validate if a request can continue.
Due to Go HTTP client being strict to the HTTP SPEC, the response of a HEAD does not include a body, while Traefik expects a validation response to be embedded, causing errors.
To mitigate this, when a X-Forwarded-Method is set as HEAD, we'll avoid modifying the HTTP Method response in order to send a body back, allowing head requests to by validated.
This is necessary even if an allow rule is set, otherwhise it will fail as well.
Mitagates: https://github.com/thomseddon/traefik-forward-auth/issues/156