Traefik 2.2.10 bug in middleware headers.customrequestheaders

Hello i was using this label for rancher service for some time now (websocket connection).

traefik.http.middlewares.rancher01.headers.customrequestheaders.X-Forwarded-Proto: "https"

I updated traefik to version 2.2.10 (docker image) today.
This label in a docker-compose file for the rancher service seems to throw some go exeptions in traefik:
i also tried a "new" middleware

traefik.http.middlewares.rancher01.headers.SSLProxyHeaders.X-Forwarded-Proto: "https"

is this the correct syntax?
Everything was/is working fine with version 2.2.8 of traefik.

Best regards

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.