On Jan 26, 2011, at 1:09 AM, Willy Tarreau wrote:
Hi Roy,
On Sun, Jan 23, 2011 at 10:04:57AM -0500, Roy Smith wrote:
Cool. What can I do to help?
Could you try to identify precisely how it would be used at your site ?
Try to think about these cases :
- what to do with reqids that are
Hi Roy,
On Thu, Jan 27, 2011 at 02:51:37PM -0500, Roy Smith wrote:
Try to think about these cases :
- what to do with reqids that are already present in requests
I don't see how that would happen. Maybe if we did something like stack one
haproxy behind another, but I don't see any
It sounds like you have given this more thought than I have (for which I am
grateful).
Still, my need is for a unique tag. If you provide me with a unique tag which
also encodes some useful information about source and time, and is guaranteed
not to roll over in the face of a flood attack,
On Thu, Jan 27, 2011 at 05:55:23PM -0500, Roy Smith wrote:
It sounds like you have given this more thought than I have (for which I am
grateful).
Still, my need is for a unique tag. If you provide me with a unique tag
which also encodes some useful information about source and time, and
Cool. What can I do to help?
On Jan 23, 2011, at 12:51 AM, Willy Tarreau wrote:
Hi Roy,
On Sat, Jan 22, 2011 at 05:26:12PM -0500, Roy Smith wrote:
Is there a way to have haproxy generate (and log) a unique ID for every
incoming request, and add that ID as a header line to each outgoing
Hi Roy,
On Sat, Jan 22, 2011 at 05:26:12PM -0500, Roy Smith wrote:
Is there a way to have haproxy generate (and log) a unique ID for every
incoming request, and add that ID as a header line to each outgoing proxied
request, i.e. something like:
X-Unique-ID: 12345ABCDE
It doesn't matter
6 matches
Mail list logo
