Revision as of 17:10, 14 May 2025 edit 79.148.167.111 (talk) →Content-Encoding tokens: Add lzip compression ← Previous edit		Revision as of 05:55, 18 May 2025 edit undo William Avery (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers 501,789 edits →Problems preventing the use of HTTP compression Next edit →
Line 86: A 2009 article by Google engineers Arvind Jain and Jason Glasgow states that more than 99 person-years are wasted<ref name="google-use-compression">{{cite web\|url=https://developers.google.com/speed/articles/use-compression\|title=Use compression to make the web faster\|access-date=22 May 2013\|publisher=Google Inc.}}</ref> daily due to increase in page load time when users do not receive compressed content. This occurs when anti-virus software interferes with connections to force them to be uncompressed, where proxies are used (with overcautious web browsers), where servers are misconfigured, and where browser bugs stop compression being used. Internet Explorer 6, which drops to HTTP 1.0 (without features like compression or pipelining) when behind a proxy – a common configuration in corporate environments – was the mainstream browser most prone to failing back to uncompressed HTTP.<ref name="google-use-compression" /> Another problem found while deploying HTTP compression on large scale is due to the '''deflate''' encoding definition: while HTTP 1.1 defines the '''deflate''' encoding as data compressed with deflate (RFC 1951) inside a [[zlib]] formatted stream (RFC 1950), Microsoft server and client products historically implemented it as a "raw" deflated stream,<ref>{{cite web\|url=https://stackoverflow.com/questions/9170338/why-are-major-web-sites-using-gzip/9186091#9186091\|title=deflate - Why are major web sites using gzip?\|publisher=Stack Overflow\|access-date=18 April 2014}}</ref> making its deployment unreliable.<ref>{{cite web\|url=http://www.vervestudios.co/projects/compression-tests/\|title=Compression Tests: About\|publisher=Verve Studios\|archive-url=https://web.archive.org/web/20150102111552/http://www.vervestudios.co/projects/compression-tests/\|archive-date=2 January 2015\|access-date=18 April 2014}}</ref><ref>{{cite web\|url=http://zoompf.com/blog/2012/02/lose-the-wait-http-compression\|title=Lose the wait: HTTP Compression\|publisher=Zoompf Web Performance\|access-date=18 April 2014}}</ref> For this reason, some software, including the Apache HTTP Server, only ~~implement~~implements '''gzip''' encoding. ==Security implications==

HTTP compression: Difference between revisions