varnish-bugs at varnish-cache
Aug 6, 2013, 2:56 AM
Post #3 of 3
(9 views)
Permalink
|
|
Re: #1325: varnishlog -m option stopped working
[In reply to]
|
|
#1325: varnishlog -m option stopped working
------------------------+-----------------------------------------
Reporter: xani | Owner: Tollef Fog Heen <tfheen@…>
Type: defect | Status: closed
Priority: normal | Milestone:
Component: varnishlog | Version: 3.0.4
Severity: normal | Resolution: fixed
Keywords: |
------------------------+-----------------------------------------
Changes (by Tollef Fog Heen <tfheen@…>):
* owner: => Tollef Fog Heen <tfheen@…>
* status: new => closed
* resolution: => fixed
Comment:
In [412c4f754dd805e06803efa170e5d62afd23dd0d]:
{{{
#!CommitTicketReference repository=""
revision="412c4f754dd805e06803efa170e5d62afd23dd0d"
Emit BackendXID and check c_flag/b_flag properly
07d488cb96c703dd7c0ccf7049448c6291f1f0cf partially broke varnishlog,
since libvarnishapi did not properly check if both -c and -b were
given.
In addition, varnishd did not emit a tag at the start of a backend
transaction. Emit BackendXID since that seems appropriate.
Fixes #1325
}}}
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1325#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
_______________________________________________
varnish-bugs mailing list
varnish-bugs [at] varnish-cache
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs
|
