RE: Re: Strange Opera error in POST

2008-06-10 Thread duja
Sure, will do that as soon as possible.

Duja

Original Message ---

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

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Strange Opera error in POST

2008-06-09 Thread Erik Torlen
Ok, I have gathered some more info about the problem.

What I have is a form login that has 3 input fields, username, password 
and security code (from captcha).

When opera is making the POST it receives a 200 OK and NOT a 302 Moved 
Temp. as expected.

This is the request that Opera is making:

   13 RxRequestc POST
   13 RxURLc /takelogin.php
   13 RxProtocol   c HTTP/1.1
   13 RxHeader c User-Agent: Opera/9.27 (Windows NT 5.1; U; sv)
   13 RxHeader c Host: mydomain.com:8080
   13 RxHeader c Accept: text/html, application/xml;q=0.9, 
application/xhtml+xml, image/png, image/jpeg, image/gif, 
image/x-xbitmap, */*;q=0.1
   13 RxHeader c Accept-Language: sv-SE,sv;q=0.9,en;q=0.8
   13 RxHeader c Accept-Charset: iso-8859-1, utf-8, utf-16, *;q=0.1
   13 RxHeader c Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0
   13 RxHeader c Referer: http://mydomain.com:8080/login.php
   13 RxHeader c Cookie: PHPSESSID=f3a60f178adede632c761dca745054cf
   13 RxHeader c Cookie2: $Version=1
   13 RxHeader c Connection: Keep-Alive, TE
   13 RxHeader c TE: deflate, gzip, chunked, identity, trailers
   13 RxHeader c Content-Length: 63
   13 RxHeader c Content-Type: application/x-www-form-urlencoded

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.

Here is the whole error log:
0 CLI  - Rd ping
0 CLI  - Wr 0 200 PONG 1213029670
   13 SessionClose - timeout
   13 StatSess - 82.182.xx.xx 1306 0 1 2 0 0 2 744 6750
0 CLI  - Rd ping
0 CLI  - Wr 0 200 PONG 1213029673
   13 SessionOpen  c 82.182.xx.xx 1307 0.0.0.0:8080
   13 ReqStart c 82.182.xx.xx 1307 803913450
   13 RxRequestc POST
   13 RxURLc /takelogin.php
   13 RxProtocol   c HTTP/1.1
   13 RxHeader c User-Agent: Opera/9.27 (Windows NT 5.1; U; sv)
   13 RxHeader c Host: mydomain.com:8080
   13 RxHeader c Accept: text/html, application/xml;q=0.9, 
application/xhtml+xml, image/png, image/jpeg, image/gif, 
image/x-xbitmap, */*;q=0.1
   13 RxHeader c Accept-Language: sv-SE,sv;q=0.9,en;q=0.8
   13 RxHeader c Accept-Charset: iso-8859-1, utf-8, utf-16, *;q=0.1
   13 RxHeader c Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0
   13 RxHeader c Referer: http://mydomain.com:8080/login.php
   13 RxHeader c Cookie: PHPSESSID=f3a60f178adede632c761dca745054cf
   13 RxHeader c Cookie2: $Version=1
   13 RxHeader c Connection: Keep-Alive, TE
   13 RxHeader c TE: deflate, gzip, chunked, identity, trailers
   13 RxHeader c Content-Length: 63
   13 RxHeader c Content-Type: application/x-www-form-urlencoded
   13 VCL_call c recv
   13 VCL_return   c pass
   13 VCL_call c pass
   13 VCL_return   c pass
   14 TxRequest- POST
   14 TxURL- /takelogin.php
   14 TxProtocol   - HTTP/1.1
   14 TxHeader - User-Agent: Opera/9.27 (Windows NT 5.1; U; sv)
   14 TxHeader - Host: mydomain.com:8080
   14 TxHeader - Accept: text/html, application/xml;q=0.9, 
application/xhtml+xml, image/png, image/jpeg, image/gif, 
image/x-xbitmap, */*;q=0.1
   14 TxHeader - Accept-Language: sv-SE,sv;q=0.9,en;q=0.8
   14 TxHeader - Accept-Charset: iso-8859-1, utf-8, utf-16, *;q=0.1
   14 TxHeader - Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0
   14 TxHeader - Referer: http://mydomain.com:8080/login.php
   14 TxHeader - Cookie: PHPSESSID=f3a60f178adede632c761dca745054cf
   14 TxHeader - Cookie2: $Version=1
   14 TxHeader - Content-Type: application/x-www-form-urlencoded
   14 TxHeader - X-Varnish: 803913450
   14 TxHeader - X-Forwarded-For: 82.182.xx.xx
   14 RxProtocol   - HTTP/1.1
   14 RxStatus - 200
   14 RxResponse   - OK
   14 RxHeader - Date: Mon, 09 Jun 2008 16:41:14 GMT
   14 RxHeader - Server: Apache
   14 RxHeader - X-Powered-By: PHP/5.2.0-8+etch10
   14 RxHeader - Content-Length: 23
   14 RxHeader - Content-Type: text/html; charset=UTF-8
   13 ObjProtocol  c HTTP/1.1
   13 ObjStatusc 200
   13 ObjResponse  c OK
   13 ObjHeaderc Date: Mon, 09 Jun 2008 16:41:14 GMT
   13 ObjHeaderc Server: Apache
   13 ObjHeaderc X-Powered-By: PHP/5.2.0-8+etch10
   13 ObjHeaderc Content-Type: text/html; charset=UTF-8
   14 BackendReuse - mydomain
   13 TTL  c 803913450 RFC 120 1213029674 1213029674 0 0 0
   13 VCL_call c fetch
   13 VCL_return   c pass
   13 Length   c 23
   13 VCL_call c deliver
   13 VCL_return   c deliver
   13 TxProtocol   c HTTP/1.1
   13 TxStatus c 200
   13 TxResponse   c OK
   13 TxHeader c Server: Apache
 

Re: Strange Opera error in POST

2008-06-09 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], 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
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Strange Opera error in POST

2008-06-09 Thread Erik Torlen
Yes, Im aware of that. But I did have some problem in an earlier version 
of trunk (and especially 1.1.2), but with the latest it seems better.

I have seen alot of updates on trunk the latest days, what's the status 
of it, is it stable for production use?

/ Duja

Poul-Henning Kamp skrev:
 In message [EMAIL PROTECTED], 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.

   

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Strange Opera error in POST

2008-06-09 Thread Erik Torlen
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 [EMAIL PROTECTED], 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.

   

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Strange Opera error in POST

2008-06-09 Thread 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 [EMAIL PROTECTED], 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 [EMAIL PROTECTED], 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
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc