-
Notifications
You must be signed in to change notification settings - Fork 302
Strict-Transport-Security header gets mangled #194
Comments
Hello, Also for "nginx_http_params", there is no post treatment with \n, you were meaning "nginx_configs" or "nginx_sites" instead ? |
We saw #135 but we couldn't understand how that helped us! Sorry, we might be being stupid, but we weren't sure what to do. After digging deeper it turns out we have it in nginx_http_params AND the site itself, so we can remove it from the site and leave it in the http_params section and that should fix this. I don't know why we put it in two places! |
|
For anyone else who comes across this, here's what I did:
Switching the whole ssl config over to multiline notation seems to produce the desired result. |
You don't need to move the whole config over to multiline notation you can mix and match. Just make sure to put an ending
|
Hi, we have the following variable set:
And this gets turned into:
Is there a way to escape or exclude a ; from being parsed in templates/site.conf.j2? I assume it's getting hit by:
To add the \n no matter what. This is causing us to have an incorrect header that breaks Cloudflare.
The text was updated successfully, but these errors were encountered: