summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2016-11-16 00:17:37 -0600
committerMichael Merickel <michael@merickel.org>2016-11-16 00:17:37 -0600
commit8dfcfb9cf823175bb91ba39565524ff95a920809 (patch)
treedc07340a8af26aa2e300cb71edd812e9738e9641 /CHANGES.txt
parent917a473262c82b7be1ff35789b18c08f9c1302dc (diff)
downloadpyramid-8dfcfb9cf823175bb91ba39565524ff95a920809.tar.gz
pyramid-8dfcfb9cf823175bb91ba39565524ff95a920809.tar.bz2
pyramid-8dfcfb9cf823175bb91ba39565524ff95a920809.zip
clarify the changes in #2810 as bw-incompatible
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt15
1 files changed, 9 insertions, 6 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index f2f412359..1939ad125 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -26,6 +26,15 @@ Backward Incompatibilities
``pyramid.static.static_view``. This argument was shipped accidentally
in Pyramid 1.6. See https://github.com/Pylons/pyramid/pull/2681
+- Change static view to avoid setting the ``Content-Encoding`` response header
+ to an encoding guessed using Python's ``mimetypes`` module. This was causing
+ clients to decode the content of gzipped files when downloading them. The
+ client would end up with a ``foo.txt.gz`` file on disk that was already
+ decoded, thus should really be ``foo.txt``. Also, the ``Content-Encoding``
+ should only have been used if the client itself broadcast support for the
+ encoding via ``Accept-Encoding`` request headers.
+ See https://github.com/Pylons/pyramid/pull/2810
+
Features
--------
@@ -101,12 +110,6 @@ Bug Fixes
from previous orders have executed.
See https://github.com/Pylons/pyramid/pull/2757
-- Fix static view to avoid setting the ``Content-Encoding`` response header
- to an encoding guessed using Python's ``mimetypes`` module.
- This was causing clients to decode the content of gzipped files
- when downloading them.
- See https://github.com/Pylons/pyramid/pull/2810
-
Deprecations
------------