[RFE] Add WSGI environ to request_started signal emission

[jag@…]

As written, the request_started signal cannot take into account any of the specifics of the aforementioned request in a connected handler. The signal provided args should add the WSGI environ to the emitted signal to allow connected handlers to act related to the request's context.

Pull request provided here: ​https://github.com/django/django/pull/1951

[Unai Zalakain]

Suggestions noted on the PR! Assign this ticket to yourself if you are planning to work on it ;-)

[Joshua "jag" Ginsberg <jag@…>]

PR amended with suggestions. Thanks!

[Aymeric Augustin]

I'm wondering if whatever you're planning to do in the signal receiver wouldn't be better implemented in a middleware.

But maybe that's just my phobia of signals :)

[Joshua "jag" Ginsberg <jag@…>]

For many (most?) cases, I'd agree with you - middleware has that explicitness, where as signals are automated magic. However the signal is the absolute earliest place to modify the handling of a request - for cases where middleware may even be too late, doing work with a signal handler could be the best option.

[Tim Graham]

I left comments for improvement on the PR. Please uncheck "Patch needs improvement" when you update it, thanks.

[Tim Graham <timograham@…>]

In eb2af16c59c3014541e2ad8ca63e510bc076dd8b:

Fixed #21483 -- Added WSGI environ to kwargs sent to request_started signal.