Hi,

I have the same problem. I'm pretty sure the problem is with Chrome latest 
version (16). I have no problem with Chrome 15.

If I look at the POST data in Chrome 16 it looks like that:

POST https://www.example.com/admin/ HTTP/1.1
Origin: https://www.example.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.7 
(KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: https://www.example.com/admin/


And in Chrome 15:

POST /admin/ HTTP/1.1
Host: www.example.com
Connection: keep-alive
Content-Length: 112
Cache-Control: max-age=0
Origin: https://www.example.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.2 
(KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: https://www.example.com/admin/
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __unam=3813975-13124e9cb4f-7fd21401-1; 
__utma=226797841.1469815294.1310584327.1316098189.1322619655.5; 
__utmz=226797841.1322616655.5.2.utmcsr=www.example.com|utmccn=(referral)|utmcmd=referral|utmcct=/;
 __utma=9258313.966017050.1316113839.1323664718.1324069816.17; 
__utmz=9258313.1316113839.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); 
csrftoken=29806a534893e8691956e77771bb3275; 
sessionid=d945d23a4900fb313a5bd70504cd7210


I'll look if there's a bug report in Chrome tracker and if not, I will add one.

Etienne
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to