Shawn O. Pearce 18e822a7fe smart-http: Fix recognition of gzip encoding ... Some clients coming through proxies may advertise a different Accept-Encoding, for example "Accept-Encoding: gzip(proxy)". Matching by substring causes us to identify this as a false positive; that the client understands gzip encoding and will inflate the response before reading it. In this particular case however it doesn't. Its the reverse proxy server in front of JGit letting us know the proxy<->JGit link can be gzip compressed, while the client<->proxy part of the link is not: client <-- no gzip --> proxy <-- gzip --> JGit Use a more standard method of parsing by splitting the value into tokens, and only using gzip if one of the tokens is exactly the string "gzip". Add a unit test to make sure this isn't broken in the future. Change-Id: I30cda8a6d11ad235b56457adf54a2d27095d964e Signed-off-by: Shawn O. Pearce <spearce@spearce.org>		2011-02-15 16:32:51 -08:00
..
.settings	Run formatter on edited lines via save action	2010-08-26 12:33:09 -05:00
META-INF	daemon: Use HTTP's resolver and factory pattern	2011-02-14 18:28:21 -08:00
tst/org/eclipse/jgit/http	smart-http: Fix recognition of gzip encoding	2011-02-15 16:32:51 -08:00
.classpath	Make HTTP test project work in Eclipse	2010-01-23 11:29:25 -08:00
.gitignore	Make HTTP test project work in Eclipse	2010-01-23 11:29:25 -08:00
.project	Revert "Hide Maven target directories from Eclipse"	2010-08-28 09:50:50 +02:00
build.properties	http.test: Add missing plugin.properties to build	2010-02-09 19:28:28 -08:00
org.eclipse.jgit.http--All-Tests.launch	Convert all JGit unit tests to JUnit 4	2010-12-31 14:00:05 -08:00
plugin.properties	Correct bundle, provider names to be consistent	2010-01-23 11:42:15 -08:00
pom.xml	Qualify post 0.11 builds	2011-02-12 03:30:05 +01:00