id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
33048	Documentation doesn't mention that using staticfiles' runserver doesn't use the middleware chain.	Keryn Knight	valleyofblackpanther	"I'm not sure ''why'' it doesn't use the middleware chain (but then I don't really know why it's not a middleware itself), because it makes a certain class of development tooling (ie: tracking responses which are assets) more difficult (I think I might have to monkeypatch? ugh), but hey ho. 

It would be nice if there were an admonition in [https://docs.djangoproject.com/en/dev/howto/static-files/#serving-static-files-during-development the Serving static files during development docs] to say as much, especially given that if you ''don't'' have `django.contrib.staticfiles` in your `INSTALLED_APPS` and instead have opted for using `+= static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)` for whatever reason, those requests **do** go through the middleware chain.

Perhaps worth noting that the subject came up independently in #32891 and despite reading that thread, I'd entirely forgotten that `staticfiles` was abnormal in that respect, in just 8 weeks...

Of course, I'm also open to changing it to go through the middleware chain like a normal request (which would look to involve removing `get_response` in favour of `resolve_request` ... or just changing it to be a middleware) ;)"	Cleanup/optimization	closed	Documentation	dev	Normal	fixed			Ready for checkin	1	0	0	0	0	0