[Varnish] #1320: Varnish returns a 503 when being given a 302 by the webapp

[Varnish]

#1320: Varnish returns a 503 when being given a 302 by the webapp
-------------------+--------------------
 Reporter:  Wilb   |       Type:  defect
   Status:  new    |   Priority:  normal
Milestone:         |  Component:  build
  Version:  3.0.3  |   Severity:  normal
 Keywords:         |
-------------------+--------------------
 This morning I've been looking to put Varnish in front of our Liferay
 cluster, but was repeatedly seeing Varnish serve up 503 errors. After
 spending a bit of time scratching my head over I came to realise that it
 was happening whenever Liferay served up a 302 redirect. This led me to
 the following unanswered thread on the mailing list:

  http://www.gossamer-threads.com/lists/varnish/misc/25910

 I was running Varnish as packaged with Debian Wheezy, which indeed is
 3.0.3. My first attempt at a fix was to upgrade to your package of 3.0.4,
 but this suffered the same problem. Dropping back down to the Squeeze
 packaged 3.0.2. from your repo fixes the issue and all is behaving well.

 When looking at varnishlog while the requests come in I see the very same
 "TestGunzip error at the very end" error whether running 3.0.3 or 3.0.4.

 The setup I was using for this was Varnish -> Apache 2.2 -> Tomcat and it
 could be reproduced by hitting /c/portal/login.

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1320>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator