Secure Headers Middleware Not Enabled by Default #837
Replies: 1 comment
-
seems like secure_headers is not enable by default, compared to this PR #785 that state what secure_headers is enabled by default. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After upgrading from version 0.9.0 to version 0.10.1, when running cargo loco middleware --config, secure_headers is disabled by default. But from the docs, it should be enabled by default.
Have been trying to add secure_headers config with enabled true, but no luck, is there any missing documentation or upgrade guide? thank you
Beta Was this translation helpful? Give feedback.
All reactions