Re: [Django] #27640: HTTPResponse.__repr__ errors when Content-Type header is not defined

[Django]

#27640: HTTPResponse.__repr__ errors when Content-Type header is not defined
-+-
 Reporter:  Adam Chainz  |Owner:  roboslone
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.10
 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:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"544b2ef29f0f2577912f88cf746ae0ca5877b5f8" 544b2ef2]:
 {{{
 #!CommitTicketReference repository=""
 revision="544b2ef29f0f2577912f88cf746ae0ca5877b5f8"
 Fixed #27640 -- Fixed HttpResponse's __repr__()  without a 'Content-Type'
 header.
 }}}

--
Ticket URL: 
Django 
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/068.8c459aec03c3cc9332efb0673bd19c6c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27640: HTTPResponse.__repr__ errors when Content-Type header is not defined

[Django]

#27640: HTTPResponse.__repr__ errors when Content-Type header is not defined
-+-
 Reporter:  Adam Chainz  |Owner:  roboslone
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


--
Ticket URL: 
Django 
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/068.b9fd8f158edb2e1d9565feccedfd79cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27640: HTTPResponse.__repr__ errors when Content-Type header is not defined

[Django]

#27640: HTTPResponse.__repr__ errors when Content-Type header is not defined
---+-
 Reporter:  Adam Chainz|Owner:  roboslone
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by roboslone):

 * has_patch:  0 => 1


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]).

 [https://github.com/django/django/pull/7746 PR]

--

--
Ticket URL: 
Django 
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/068.3d9932bd4636190e3cbad4b531fdfd38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27640: HTTPResponse.__repr__ errors when Content-Type header is not defined

[Django]

#27640: HTTPResponse.__repr__ errors when Content-Type header is not defined
---+-
 Reporter:  Adam Chainz|Owner:  roboslone
 Type:  Bug|   Status:  assigned
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 roboslone):

 * owner:  nobody => roboslone
 * status:  new => assigned


--
Ticket URL: 
Django 
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/068.3808a9c6349c5677abcee0ff7fd5eed7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27640: HTTPResponse.__repr__ errors when Content-Type header is not defined

[Django]

#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: 
Django 
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/068.0041654c600b15b214a87c7a521d269e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.