#36456: Improve content type negotiation for 500 response
-------------------------------------+-------------------------------------
Reporter: Jake Howard | Type:
| Cleanup/optimization
Status: new | Component: HTTP
| handling
Version: dev | Severity: Normal
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
`django.views.debug.technical_500_response` supports either a HTML or
plain text output. Currently, the client will be served HTML if they
support it, even if they preferred a plain text response.
Ideally, the user would be served HTML if it is their preference of the 2,
otherwise they'd be served plain text. If for whatever reason neither are
supported, serve plain text. This can be done with
`request.get_preferred_type`.
--
Ticket URL: <https://code.djangoproject.com/ticket/36456>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701975fbfa7d8-834a0882-a22b-4956-8d22-f14aee2a4368-000000%40eu-central-1.amazonses.com.
