With channels, runserver is not longer using WSGIRequest about channels

[andrewgodwin]

Well, request.environ is not part of the public Request API so I was trying not to provide it (for example, a test client request isn't a WSGIRequest either). Why do you need it? All the things it provides appear in META, pretty much.

[bastianh]

The library I'm using is using it, I guess it's also possible to change that or use my own but I wasn't sure if that's the only difference.

https://github.com/jrief/django-angular/blob/master/djangular/middleware.py

[andrewgodwin]

Yeah, that library is using undocumented features; they're manually rebuilding requests, which just isn't going to integrate with Channels very well. There's not much I can do to support that yet, really; hopefully once we have a clear outline of how requests will differ in a non-WSGI environment I can contribute pull requests to projects like these to help them use things via documented APIs.

For what it's worth, I don't know why they don't mutate the Request object on the fly like other middlewares do, but there might be a good reason for it.

[knbk]

request.META is the same dict (not just a copy, but the same object) as request.environ. Any app that uses request.environ can switch to request.META without any issues.

[andrewgodwin]

Right; there's no need for .environ at all, from what I understand.