#36456: Improve content type negotiation for 500 response
-------------------------------------+-------------------------------------
Reporter: Jake Howard | Owner: Johanan
Type: | Oppong Amoateng
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"be8c9b19baeb4daf6bf2e603673714c7536b657c" be8c9b19]:
{{{#!CommitTicketReference repository=""
revision="be8c9b19baeb4daf6bf2e603673714c7536b657c"
Fixed #36456 -- Improved content type negotiation in technical 500 error
response.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36456#comment:6>
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/010701981c9cfa91-259526a1-805c-443f-a223-8f08fba64571-000000%40eu-central-1.amazonses.com.
