Commit a4c57ecc authored by Tollef Fog Heen's avatar Tollef Fog Heen

Fix up syntax for matching in docs

parent 0b1d5427
...@@ -86,13 +86,13 @@ The "varnishlog" utility may produce a horrendous amount of output. To be able ...@@ -86,13 +86,13 @@ The "varnishlog" utility may produce a horrendous amount of output. To be able
The ReqStart token will include the client IP address. To see log entries matching this, type:: The ReqStart token will include the client IP address. To see log entries matching this, type::
$ varnishlog -c -o ReqStart 192.0.2.123 $ varnishlog -c -m ReqStart:192.0.2.123
To see the backend requests generated by a client IP address, we can match on the TxHeader token, since the IP address of the client is included in the X-Forwarded-For header in the request sent to the backend. To see the backend requests generated by a client IP address, we can match on the TxHeader token, since the IP address of the client is included in the X-Forwarded-For header in the request sent to the backend.
At the shell command line, type:: At the shell command line, type::
$ varnishlog -b -o TxHeader 192.0.2.123 $ varnishlog -b -m TxHeader:192.0.2.123
**How can I rewrite URLS before they are sent to the backend?** **How can I rewrite URLS before they are sent to the backend?**
......
...@@ -80,13 +80,13 @@ give you a clue. Since varnishlog logs so much data it might be hard ...@@ -80,13 +80,13 @@ give you a clue. Since varnishlog logs so much data it might be hard
to track the entries down. You can set varnishlog to log all your 503 to track the entries down. You can set varnishlog to log all your 503
errors by issuing the following command::: errors by issuing the following command:::
$ varnishlog -c -o TxStatus 503 $ varnishlog -c -m TxStatus:503
If the error happened just a short time ago the transaction might still If the error happened just a short time ago the transaction might still
be in the shared memory log segment. To get varnishlog to process the be in the shared memory log segment. To get varnishlog to process the
whole shared memory log just add the -d option::: whole shared memory log just add the -d option:::
$ varnishlog -d -c -o TxStatus 503 $ varnishlog -d -c -m TxStatus:503
Please see the varnishlog man page for elaborations on further Please see the varnishlog man page for elaborations on further
filtering capabilities and explanation of the various options. filtering capabilities and explanation of the various options.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment