You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traefik serving traffic and registering the docker backend.
What did you see instead?
docker backend doesn't get registered. I get the following in my log:
time="2017-11-29T20:39:10Z" level=error msg="Near line 256 (last key parsed 'frontends.frontend-Host-hostname-8.headers.ReferrerPolicy'): expected value but found "no" instead"
Output of traefik version: (What version of Traefik are you using?)
And that doesn't give an error. I get the same error if I try to apply the following XFO header: "ALLOW-FROM https://domain.name/"
Removing the XFO and the Referrer policy from the container tags fixes the issue.
If applicable, please paste the log output in debug mode (--debug switch)
time="2017-11-29T20:45:37Z" level=error msg="Near line 624 (last key parsed 'frontends.frontend-Host-hostname.headers.ReferrerPolicy'): expected value but found "no" instead"
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
What did you do?
Container has the following labels:
What did you expect to see?
Traefik serving traffic and registering the docker backend.
What did you see instead?
docker backend doesn't get registered. I get the following in my log:
Output of
traefik version
: (What version of Traefik are you using?)What is your environment & configuration (arguments, toml, provider, platform, ...)?
Applying the following configuration via terraform:
I'm applying the same header via the file backend for another frontend:
And that doesn't give an error. I get the same error if I try to apply the following XFO header:
"ALLOW-FROM https://domain.name/"
Removing the XFO and the Referrer policy from the container tags fixes the issue.
If applicable, please paste the log output in debug mode (
--debug
switch)The text was updated successfully, but these errors were encountered: