[Varnish] #250: POST error when using Opera

Varnish varnish-bugs at projects.linpro.no
Sat Jun 21 18:32:29 CEST 2008

#250: POST error when using Opera
 Reporter:  duja    |        Owner:  des                
     Type:  defect  |       Status:  new                
 Priority:  normal  |    Milestone:  Varnish 2.0 release
Component:  build   |      Version:  trunk              
 Severity:  normal  |   Resolution:                     
 Keywords:          |  
Comment (by phk):

 First, why do you insert the Connection: closed in the first place ?  That
 trick only makes sense with "pipe" method.

 But irrespective of this, I have a hard time seeing what it does, because
 both the Connection and TE headers are already filtered out going through
 Varnish (notice how they are not in the TXheaders, so the backend will
 receive the same request either way.

 As to 200 vs 302 reply, that seems to be entirely up to the backend to
 decide, apart from what gets sent to the backend, I can't see how Varnish
 is or can be involved in that.

 As for deleting the Cookie2 and TE headers, Varnish never inspects either,
 and the latter is not sent to the backend, so I don't understand why you
 would have to remove TE and assume that the backend reacts to the lack of
 Cookie2 header.

 My best suggestion is that you capture varnishlog output from a client
 that works and compare it to this, and then examine what the backend
 actually does when it is called.

 I don't see anything that indicates that varnish is doing anything

Ticket URL: <http://varnish.projects.linpro.no/ticket/250#comment:2>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list