[Varnish] #255: Varnish segfaults on certain response header sets

[Varnish]

#255: Varnish segfaults on certain response header sets
-----------------------+----------------------------------------------------
 Reporter:  rafrombrc  |        Owner:  phk  
     Type:  defect     |       Status:  new  
 Priority:  normal     |    Milestone:       
Component:  varnishd   |      Version:  trunk
 Severity:  critical   |   Resolution:       
 Keywords:             |  
-----------------------+----------------------------------------------------
Comment (by rafrombrc):

 whoops, the header lists got mangled, let's try that again.  here are the
 headers that work:

 {{{
 Outgoing headers: (200 OK)
   Server: Zope/(Zope 2.10.5-final, python 2.4.4, linux2) ZServer/1.1
 Plone/3.0.7 (svn/unreleased)
   Date: Thu, 19 Jun 2008 21:14:49 GMT
   Content-Length: 18347
   Expires: Mon, 22 Jun 1998 21:14:49 GMT
   Last-Modified: Sun, 27 Nov 2005 05:41:47 GMT
   X-Caching-Rule-Id: 7
   Cache-Control: max-age=0, s-maxage=3600, must-revalidate
   Content-Type: text/html; charset=utf-8
   X-Header-Set-Id: cache-in-proxy-1-hour
 }}}

 and here are the headers that cause the segfault:

 {{{

 Outgoing headers: (200 OK)
   Server: Zope/(Zope 2.10.5-final, python 2.4.4, linux2) ZServer/1.1
 Plone/3.0.7 (svn/unreleased)
   Date: Thu, 19 Jun 2008 21:14:49 GMT
   Content-Length: 18347
   Expires: Thu, 19 Jun 2008 21:14:49 GMT
   Last-Modified: Sun, 27 Nov 2005 05:41:47 GMT
   X-Caching-Rule-Id: 7
   Cache-Control: must-revalidate, max-age = 0
   Content-Type: text/html; charset=utf-8
   X-Header-Set-Id: cache-in-proxy-1-hour
 }}}

 again, you'll notice that the only difference btn the header sets is the
 Cache-Control and the Expires headers.

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/255#comment:1>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator