Opened 16 years ago
Closed 14 years ago
#10937 closed (fixed)
Recommendation of mod_wsgi is incompatible with apache-authentication technique described in docs
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | 1.0 |
Severity: | Keywords: | deployment mod_python mod_wsgi | |
Cc: | sam@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I found this documentation about authenticating in apache using Django
http://docs.djangoproject.com/en/1.0//howto/apache-auth/#howto-apache-auth
However, since Django is now recommending mod_wsgi in favor of mod_python, the techniques described here no longer work (if mod_python is not installed).
I don't know enough of mod_wsgi or mod_python to have a solution – I suggest you ask Graham for this –, but at least change the docs to mention that you'll need mod_python installed instead of mod_wsgi for this to work.
Change History (5)
comment:1 by , 16 years ago
comment:2 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 15 years ago
There is some crossover here between this ticket and #10809. I think the fix for that ticket should cover this ticket as well.
comment:4 by , 14 years ago
Keywords: | deployment added |
---|
See:
I believe there may be a separate Django ticket somewhere already about documenting how to do the authentication against Django when using mod_wsgi.
Do note though that that access control mechanism works in embedded mode. If you are running Django in daemon mode it would be a bit stupid to be doing it that way.