Opened 9 years ago
Closed 9 years ago
#26307 closed New feature (wontfix)
More explicit HTTPS deployment documentation
Reported by: | Takis Issaris | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Although the Django security documentation recommends using HTTPS , the deployment documentation does not explain how to actually deploy Django using HTTPS. Now, one could argue that it is out of the documentation's scope to specify how to setup HTTPS with a specific HTTP-server, but the documentation does contain information on setting up with f.e. Apache.
This seems to have become more important now that f.e. Google and Mozilla are pushing for using HTTPS by default for all sites.
https://docs.djangoproject.com/en/1.9/topics/security/#ssl-https
https://docs.djangoproject.com/en/1.9/howto/deployment/
Change History (1)
comment:1 by , 9 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Type: | Uncategorized → New feature |
As far as I know there is nothing Django specific related to configuring SSL on a frontend webserver, so I think it's better to consult your webserver's documentation instead of duplicating that information in Django's docs.