[prev in list] [next in list] [prev in thread] [next in thread] 

List:       varnish-bugs
Subject:    Re: [Varnish] #416: Segfault
From:       "Varnish" <varnish-bugs () varnish-cache ! org>
Date:       2013-12-17 11:51:28
Message-ID: 056.89ca6544a4b756eb790b2b500d102a7b () varnish-cache ! org
[Download RAW message or body]

#416: Segfault
--------------------+---------------------
 Reporter:  sky     |       Owner:  sky
     Type:  defect  |      Status:  closed
 Priority:  normal  |   Milestone:
Component:  build   |     Version:  2.0
 Severity:  normal  |  Resolution:  fixed
 Keywords:          |
--------------------+---------------------
Changes (by Poul-Henning Kamp <phk@…>):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [15d6c830476bda06c40dbb70ee4bd6be38d6e93e]:
 {{{
 #!CommitTicketReference repository=""
 revision="15d6c830476bda06c40dbb70ee4bd6be38d6e93e"
 When we get a bogus reply from a backend, for instance with too many
 headers, we need to purge all traces of it, before we construct our
 503 response, otherwise we risk failing to set important headers,
 such as "Connection: close".

 Fixes #416
 (again)
 }}}

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/416#comment:7>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs
[prev in list] [next in list] [prev in thread] [next in thread]