Strange Opera error in POST

[Poul-Henning Kamp]

Can I get you to record a varnish log where you do that and one 
where you don't, and then open a ticket with this issue ?

Poul-Henning

In message <484D83C6.8030301 at torlen.net>, Erik Torlen writes:
>What I should mention is that the problem can be solved by another method.
>
>If I remove the Cookie2 AND TE header it all works out fine:
>
>       remove req.http.Cookie2;
>       remove req.http.TE;
>
>        if(req.request != "GET" && req.request != "HEAD") {
>                set req.http.Connection = "close";
>                pass;
>        }
>
>This works!
>
>But I must remove BOTH Cookie2 and TE header, else it wont work.
>
>/ Duja
>
>Poul-Henning Kamp skrev:
>> In message <484D7E2A.3060804 at torlen.net>, Erik Torlen writes:
>>
>>   
>>> My vcl has this code when POST are received:
>>>
>>>        if(req.request != "GET" && req.request != "HEAD") {
>>>                set req.http.Connection = "close";
>>>                pass;
>>>        }
>>>
>>> This code usually works with FF and IE but NOT with Opera.
>>>
>>> If I remove "set req.http.Connection = "close";"
>>>
>>> the login process works with no problem.
>>>
>>> I have had problems with POSTs before, thats why I've been using 
>>> Connection = "close" on POSTs.
>>>     
>>
>> I'm not sure I can say much here...
>>
>> The "close" trick is mostly, if not only, relevant for "pipe" mode,
>> where it prevents more than the first request from the client from
>> being piped.  It doesn't really do anything positive for "pass".
>>
>>   
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.