Le 22 oct. 2012 à 23:50, Aymeric Augustin <aymeric.augus...@polytechnique.org> a écrit :
> There's encoding information available both in self._charset and in the > Content-Encoding header. I was confused — Content-Encoding is typically "gzip" of "deflate"; it has nothing to do with the response charset. For all practical values of Content-Encoding [1], the content is compressed binary data, which must be represented as bytes. I don't see any reason to support any other data type when a Content-Encoding is set. I've written a patch for #18796 [2] and I plan to commit it before the feature freeze. [1] http://en.wikipedia.org/wiki/HTTP_compression#Content-coding_tokens [2] https://code.djangoproject.com/attachment/ticket/18796/18796.patch -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
