| 1 |
This is a new feature (in v5.3.4 onwards) which can help in trouble shooting |
| 2 |
|
| 3 |
It would not normally be turned on on production systems, except when |
| 4 |
diagnosing any sudden-death symptoms. |
| 5 |
|
| 6 |
Enable by defining rqloglocation in e2guardian.conf |
| 7 |
|
| 8 |
This log will be in the same format as access.log. It shows all requests |
| 9 |
before any processing is performed. |
| 10 |
|
| 11 |
The filtergroup should be ignored as it will normally show the default group |
| 12 |
as the record is wriiten to the log before any authentication plug-ins are |
| 13 |
actioned. |
| 14 |
|
| 15 |
The following information is provided in the 'what' field:- |
| 16 |
|
| 17 |
thread_id - allows thread to be followed and also cross-matched to syslog and |
| 18 |
access.log |
| 19 |
|
| 20 |
TRANS, PROXY, THTTPS, MITM, REQMOD or RESPMOD showing the source of the |
| 21 |
request |
| 22 |
|
| 23 |
TRANS - transparent http |
| 24 |
|
| 25 |
PROXY - requests via the normal proxy port(s) (8080 etc) - includes |
| 26 |
transparent http |
| 27 |
|
| 28 |
THTTPS - requests via tranparent https port + flags for presence of TLS |
| 29 |
and SNI |
| 30 |
|
| 31 |
MITM - requests from within a MITM session (can be via PROXY or THTTPS) |
| 32 |
|
| 33 |
REQMOD - requests to ICAP REQMOD service |
| 34 |
|
| 35 |
RESPMOD - requests to ICAP RESPMOD service |
| 36 |
|
| 37 |
WARNING - this option also modifies the access.log! |
| 38 |
|
| 39 |
With this option active the thread_id is also added to the front of the 'what' |
| 40 |
field in the access.log to allow cross-checking between the logs. |