#14506: Crash on HEAD request
------------------------------------+---------------------------------------
Reporter: azurit | Owner: nobody
Status: reopened | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by kmtracey):
Replying to [comment:4 azurit]:
> Replying to [comment:3 jezdez]:
> > Looks like request.user is not set. Which means the Auth middleware
was not successfully run.
> [[BR]]
> Yes, Auth middleware is NOT loaded.
If you don't have the auth middleware loaded, why do you have the XView
middleware loaded (that's the code that is generating the exception)? That
middleware is documented
(http://docs.djangoproject.com/en/dev/ref/middleware/#django.middleware.doc.django.middleware.doc.XViewMiddleware)
as providing some function for the admindocs feature, which is only
accessible from admin, which requires the auth middleware to be in place.
So XView assumes auth middleware is loaded.
Leaving open since I guess the XView code could handle this more
gracefully, but the easiest fix would seem to be for you to remove it from
your middleware setting.
--
Ticket URL: <http://code.djangoproject.com/ticket/14506#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
