req.hash not a string (when?)

Poul-Henning Kamp phk at phk.freebsd.dk
Thu Aug 12 08:24:25 CEST 2010


In message <AANLkTimCQKs3R0HDSWU0S-AV6M2CpW_mt1a5_FoJWfM5 at mail.gmail.com>, "T. 
Pascal" writes:
>On Wed, Aug 11, 2010 at 2:31 PM, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
>> In message <AANLkTin6VUioE8hbWeU+bhKM4g8C5uOeTbkqjSkKmHsr at mail.gmail.com>, "T.
>> Pascal" writes:
>>
>>>Just wondering when/if req.hash can be used like the above error (or,
>>>with the new "log" feature)?
>>
>> req.hash is not coming back as a readable variable, it is too expensive
>> in storage.
>>
>I can appreciate that; wondering if it can be emitted in varnishlog;
>currently you only see this:

There's already a parameter for that: log_hashstring

-- 
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.




More information about the varnish-dev mailing list