Data sources and objects captureEtherSensor ICAP service:
[*]Compliance with the updated draft-stecher-icap-subid-00.txt.
When the ICAP client sends the X-Subscriber-ID, X-Authenticated-User, X-Authenticated-Groups headers, they are now saved as data file properties in the passport: icap-x-subscriber-id, icap-x-authenticated-user, icap-x-authenticated-group correspondingly. If the X-Authenticated-Groups contains multiple groups, each of them is saved as a separate icap-x-authenticated-group property which contains only one group.
[+]New debug counters were added:
The number of POST requests passed by ICAP to REQMOD.
The number of PUT requests passed by ICAP to REQMOD.
The number of files opened to save POST/PUT in REQMOD.
The number of files currently open to save POST/PUT in REQMOD.
The number of files closed with the "save to cache" status (they must be in the cache).
The number of files closed with the "remove from cache" status (due to some errors).
[+]Filtering for raw-log was implemented in REQMOD. Requests to Host: icap.health.check result in the removal of raw-log files for this TCP session. The filter is currently hard-coded.
[+]Now if the ICAP client sends the X-Client-Username header, it is saved as a data file property in the icap-x-client-username passport. The header may be sent by the SQUID server if it has user authentication configured. Configuring icap_send_client_username on|off in squid.conf file. Other clients may also send this header, but we don't know it for sure.