req.hash not a string (when?)

[T. Pascal]

On Wed, Aug 11, 2010 at 11:24 PM, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
> 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
>
Confirmed that works with the "-p log_hashstring on" on startup or
"param.set log_hashstring on" in the CLI.

The "run-time parameters" part of the documentation was a bit tricky
to find, but I suddenly see what the cryptic comments about (for
example) "max_restarts" were all about.

-T