Handling 304 and header refresh
Tollef Fog Heen
tfheen at redpill-linpro.com
Thu Dec 3 09:04:22 CET 2009
]] Daniel Rodriguez
| 13 BackendOpen b default 192.168.55.18 38239 192.168.9.158 80
| 12 Backend c 13 default default
| 13 TxRequest b GET
| 13 TxURL b /test/prueba.php
| 13 TxProtocol b HTTP/1.1
| 13 TxHeader b Host: www.foo.com
| 13 TxHeader b User-Agent: Mozilla/5.0 (X11; U; Linux i686;
| en-US; rv:1.9.0.3) Gecko/2008092816 Iceweasel/3.0.3 (Debian-3.0.3-3)
| 13 TxHeader b Accept:
| text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
| 13 TxHeader b Accept-Language: en-us,en;q=0.5
| 13 TxHeader b Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
| 13 TxHeader b X-Forwarded-For: 192.168.90.41
| 13 TxHeader b Accept-Encoding: gzip
| 13 TxHeader b X-Varnish: 484826741
| 13 TxHeader b X-Forwarded-For: 192.168.90.41
| 13 RxProtocol b HTTP/1.1
| 13 RxStatus b 304
| 13 RxResponse b Not Modified
| 13 RxHeader b Date: Tue, 01 Dec 2009 10:50:33 GMT
| 13 RxHeader b Server: Apache
| 13 RxHeader b Connection: close
| 13 RxHeader b Cache-control: max-age=401
Your backend seems to reply with 304 to an unconditional GET request,
which is quite odd.
--
Tollef Fog Heen
Redpill Linpro -- Changing the game!
t: +47 21 54 41 73
More information about the varnish-misc
mailing list