#10762: Gzip Middleware Should Compress 201 (Created) Responses
-----------------------------------------------+----------------------------
Reporter: rwag...@physics.ucsd.edu | Owner: nobody
Status: new | Milestone:
Component: HTTP handling | Version: SVN
Resolution: | Keywords: middleware gzip
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------+----------------------------
Comment (by rpwagner):
Replying to [comment:1 julianb]:
> While we are at it: What about 404 or 403 responses?
I don't believe that was what was intended by the original condition. The
2XX status codes indicate successful operations, whereas 4XX are client
errors. In practice, I think it is a good idea to render errors in the
simplest formats possible, to make interpreting them easier on the client
side. But, I can see the argument for compressing a custom 404 response
that is rendered from a template, and could get large.
--Rick
--
Ticket URL: <http://code.djangoproject.com/ticket/10762#comment:2>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
