2014-07-02 15:36 GMT+02:00 Łukasz Rekucki <lreku...@gmail.com>: It doesn't just alter it, but makes it conform to HTTP standard.
As usual, given a different set of expectations, auto-fix is auto-break. We recently removed two of the four unconditional response "fixes". The remaining ones are: - `fix_location_header`: at least for some people, it's an issue. That's why we're having a discussion. - `conditional_content_removal`: there's a variety of scenarios where it fails. For instance, if you have a reverse proxy in front of your app that performs gzipping, to handle HEAD requests correctly, it must get the response body, compress it, figure out its length, and add it to the Content-Length header. That's why I believe the concept of unconditional response "fixes" in itself is flawed. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mWfbz__6_18S9Ak098Byp9NuJLumvCy3YKbq6SXUbFtTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
