Willy Tarreau 1f0da2485e BUG/MEDIUM: unique_id: HTTP request counter is not stable ... Patrick Hemmer reported that using unique_id_format and logs did not report the same unique ID counter since commit 9f09521 ("BUG/MEDIUM: unique_id: HTTP request counter must be unique!"). This is because the increment was done while producing the log message, so it was performed twice. A better solution consists in fetching a new value once per request and saving it in the request or session context for all of this request's life. It happens that sessions already have a unique ID field which is used for debugging and reporting errors, and which differs from the one sent in logs and unique_id header. So let's change this to reuse this field to have coherent IDs everywhere. As of now, a session gets a new unique ID once it is instanciated. This means that TCP sessions will also benefit from a unique ID that can be logged. And this ID is renewed for each extra HTTP request received on an existing session. Thus, all TCP sessions and HTTP requests will have distinct IDs that will be stable along all their life, and coherent between all places where they're used (logs, unique_id header, "show sess", "show errors"). This feature is 1.5-specific, no backport to 1.4 is needed.		2014-01-25 11:07:06 +01:00
..
acl.h
arg.h
auth.h
backend.h
capture.h
channel.h
checks.h
compression.h
connection.h
counters.h
fd.h
freq_ctr.h
global.h
hdr_idx.h
lb_chash.h
lb_fas.h
lb_fwlc.h
lb_fwrr.h
lb_map.h
listener.h
log.h
map.h
obj_type.h
pattern.h
peers.h
pipe.h
port_range.h
proto_http.h
proto_tcp.h
protocol.h
proxy.h
queue.h
sample.h
server.h
session.h
signal.h
ssl_sock.h
stick_table.h
stream_interface.h
task.h
template.h