#7317 closed (fixed)
XViewMiddleware should not be enabled by default.
Reported by: | anonymous | Owned by: | Jacob |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The XViewMiddleware is enabled by default and it is causing problems and confusion, see #7299 and http://toofishes.net/blog/django-middleware-order/ , quoting from there: "I don't really know what XView does, so it is last. It isn't that important.".
That's because
- it is enabled by default AND
- its purpose is too vaguely defined: Sends custom X-View HTTP headers to HEAD requests that come from IP addresses defined in the INTERNAL_IPS setting. This is used by Django’s automatic documentation system.
The middleware can be safely disabled and should be documented as such. Although I have looked at the source, I fail to see it's purpose for the general public. The only "automatic documenatation" system I have encountered is the context from exception backtraces. *If* it is used there, this should be stated -- "The automatic documentation system is mainly useful to see exception backtrace context in debug mode. You can disable it in production mode."
Please correct me if I'm wrong.
Change History (7)
comment:1 by , 16 years ago
Component: | Tools → Documentation |
---|
comment:2 by , 16 years ago
Needs documentation: | set |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
comment:3 by , 16 years ago
James explains the purpose of XViewMiddleware quite well http://www.b-list.org/weblog/2007/nov/07/bookmarklets/ . Perhaps some of it could be borrowed for documentation.
As nfa has a separate documentation app not enabled by default, XViewMiddleware should also be disabled by default and enabled only if the former is enabled.
comment:5 by , 16 years ago
milestone: | 1.0 maybe → 1.0 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Summary: | XViewMiddleware should be documented better → XViewMiddleware should not be enabled by default. |
Triage Stage: | Design decision needed → Accepted |
(changed description -- the docs are fine, but it shouldn't be on by default)
Indeed, looks like the XViewMiddleware is not used anywhere internally, perhaps it should not be enabled by default?