Skip to content
This repository has been archived by the owner on Jun 7, 2020. It is now read-only.

Not all security settings suggested by Django's check --deploy command are enabled in production #27

Open
yoowul opened this issue May 9, 2017 · 0 comments
Labels

Comments

@yoowul
Copy link
Contributor

yoowul commented May 9, 2017

Security settings proposed by django's check --deploy flag:

secure_content_type_nosniff: True
secure_browser_xss_filter: True
session_cookie_secure: True
csrf_cookie_secure: True
csrf_cookie_httponly: True
x_frame_options: DENY

Currently the first four are set to False due to errors.

@yoowul yoowul changed the title Research the implemenation of security settings proposed by django's check --deploy flag Research the implementation of security settings proposed by django's check --deploy flag May 9, 2017
@cameel cameel changed the title Research the implementation of security settings proposed by django's check --deploy flag Not all security settings suggested by Django's check --deploy command are enabled in production May 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants