Another one,
Varnishlog does not filter as advertised when using the -o option. I don't
know what it *does* do, but it most certainly isn't "to select only
requests which generated a log entry with the given
tag whose contents match the given regex." -- I just get a bunch of
entries -- seems like all of them from files, and completely random ones
from shared memory, none of which have my match even
(IP REPLACED BELOW)
varnishlog -r <LOGFILE> -o RxStatus 503
674 TxHeader - X-Varnish: 290112796
666 SessionClose - EOF
666 StatSess - X.Y.Z 51110 7 1 1 0 1 1 507 11905
660 RxProtocol - HTTP/1.1
660 RxStatus - 200
660 RxResponse - OK
660 RxHeader - X-Powered-By: PHP/5.2.11
660 RxHeader - Expires: Thu, 19 Nov 1981 08:52:00 GMT
660 RxHeader - Cache-Control: no-store, no-cache, must-revalidate,
post-check=0, pre-check=0
660 RxHeader - Pragma: no-cache
660 RxHeader - Content-Encoding: gzip
(I have around 500 hits/sec on this box)
--On Wednesday, August 04, 2010 3:42 PM -0600 Michael Loftis
<[email protected]> wrote:
If varnish receives any data on a client socket while it's sending then
it closes the socket...
I havne't tried any other test cases but happens 100% of the time on
freebsd 8.0 w/ varnish 2.1.3 simple test case, cut and paste in a GET
request, and hit enter twice, really quickly, it'll disconnect...
Anyone else seeing this? I want to check others' before I go open a bug
on it.
_______________________________________________
varnish-misc mailing list
[email protected]
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
_______________________________________________
varnish-misc mailing list
[email protected]
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
