On 06/13/2018 07:09 AM, Matus UHLAR - fantomas wrote: > On 13.06.18 13:26, Tiraen wrote: >> ICAP will help provide data on incoming / outgoing traffic? > icap can get the data and work with it. > you don't have to manipulate, just do the accounting. > you just need ICAP module that will do it. Yes, it is possible to collect more-or-less accurate incoming request and incoming response stats using an ICAP service, but doing so would be very inefficient. Using eCAP would improve performance, but interpreting live access.log streams is probably the most efficient way of doing this. IIRC, both eCAP and ICAP interfaces do not see the exact incoming requests and incoming responses because Squid may strip hop-by-hop HTTP headers and decode chunked HTTP message bodies before forwarding the incoming message to the adaptation service. If you need exact headers and exact body sizes, then you need more than just the basic ICAP and eCAP interface. Again, access.log is probably an overall better choice for capturing that info. Both eCAP and ICAP interfaces do not see outgoing requests and outgoing responses because Squid only supports pre-cache vectoring points. HTH, Alex. P.S. In the above, "incoming" is "to Squid" and "outgoing" is "from Squid". >> 2018-06-13 12:54 GMT+03:00 Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx>: >> >>> On 13.06.18 11:51, Tiraen wrote: >>> >>>> either such a question, perhaps someone in the course >>>> >>>> in the SQUID is still not implemented radius accounting? >>>> >>> >>> authentication - yes. But squid doese not support accounting (afaik). >>> >>> Maybe there are any third-party modules working correctly? >>>> >>> >>> maybe iCAP module. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
