#21250: Make Remote User tests more flexible
--------------------------------------+------------------------------------
Reporter: elbarto | Owner: elbarto
Type: Cleanup/optimization | Status: closed
Component: Testing framework | Version: 1.5
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"8f994f1bccfe4309d63433d78978109a32f0826b"]:
{{{
#!CommitTicketReference repository=""
revision="8f994f1bccfe4309d63433d78978109a32f0826b"
Fixed #21250 -- Made HTTP auth user header configurable in tests
Currently, if the authentication mechanism uses a custom HTTP header
and not REMOTE_USER, it is not easy to test. This commit modifies
remote user tests in order to make them more generic.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21250#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.caeb21b4177b58b6e721e70fc06162e0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
