#23004: Cleanse entries from request.META in debug views
------------------------------+------------------------------------
Reporter: blueyed | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by blueyed):
Just answering to the separate issue from the comment about `request.META`
- I do not have time to provide a patch for this issue myself, but thanks
for accepting it and outlining how it could be done!
> Regarding your comment, it's a separate issue but I don't think the test
client should include os.environ. You shouldn't rely on environment
variables in your views.
It's more that I want to test for e.g. `assert settings.SECRET_KEY not in
response.content` (for a "500" page), and was surprised that
`request.META` in the test client is different from runserver/uwsgi. I
have created a new issue for it:
https://code.djangoproject.com/ticket/23006
--
Ticket URL: <https://code.djangoproject.com/ticket/23004#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.b7580af7b54157dd9d115467e6a18fb5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
