#27640: HTTPResponse.__repr__ errors when Content-Type header is not defined
-------------------------------+------------------------------------
Reporter: Adam Chainz | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.10
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
-------------------------------+------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Old description:
> As reported [https://groups.google.com/forum/#!msg/django-
> developers/Dd-R-7YiQYQ/kM9PoQxiEQAJ on the mailing list],
> HTTPResponse.__repr__ crashes when the Content-Type header is not
> defined. It's legitimate that it's not defined when there is no body,
> e.g. for HTTP 204 responses
> ([https://stackoverflow.com/questions/21029351/what-content-type-
> should-a-204-no-response-use StackOverflow]).
New description:
As reported [https://groups.google.com/forum/#!msg/django-
developers/Dd-R-7YiQYQ/kM9PoQxiEQAJ on the mailing list],
`HTTPResponse.__repr__` crashes when the Content-Type header is not
defined. It's legitimate that it's not defined when there is no body, e.g.
for HTTP 204 responses ([https://stackoverflow.com/questions/21029351
/what-content-type-should-a-204-no-response-use StackOverflow]).
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27640#comment:1>
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/068.0041654c600b15b214a87c7a521d269e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
