And it only kinda works because when there is no question mark then the field will have the uri instead of being empty...
On Thu, Jul 30, 2015 at 7:12 PM, Phillip Decker < [email protected]> wrote: > Funny, yeah I was just playing with it and couldn't get that to work, so I > just did another git pull thinking maybe I just wasn't updated, then came > back to my email and saw your second reply. > > Hrm. Well, something that seems to sorta work is this (in the log-format > line): > %[capture.req.uri,regsub(^.*\?,)] > > So, grabbing the full uri and then regex replace everything up to the '?' > with nothing, but I don't know what kind of underlying impacts that > approach might have, if any... > > Phillip > > On Thu, Jul 30, 2015 at 6:25 PM, Cyril Bonté <[email protected]> wrote: > >> On 31/07/2015 00:14, Cyril Bonté wrote: >> >>> Hi Phillip, >>> >>> On 31/07/2015 00:05, Phillip Decker wrote: >>> >>>> One other log question in this same vein - >>>> >>>> I'm trying to duplicate the functionality of the %q flag in Apache, and >>>> I don't see a way in the documentation to print _only_ the query string, >>>> that is, the information after the question mark in a URI. I see the >>>> URI without the query (path), the full URI, and looking up specific >>>> parameters in the URI... am I missing an obvious flag somewhere? >>>> >>> >>> This is only available in 1.6 development branch : >>> http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#query >>> >> >> Oops, I replied too quickly, as such HTTP sample fetches are not >> available in log-format. >> Maybe we can discuss adding a %HQ (or %HQS) log variable in the future ? >> >> -- >> Cyril Bonté >> > >
