live access.log streams is probably the most efficient way of doing this.
Concerning this moment
So in the logs only one half of the traffic, and if the incoming + outgoing
https://alter.org.ua/soft/fbsd/squid_tot_sz/
https://alter.org.ua/soft/fbsd/squid_tot_sz/
All the patches I found are related to the old versions of the SQUID
for 3.5 this is not
2018-06-21 19:20 GMT+03:00 Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>:
On 06/21/2018 05:14 AM, Tiraen wrote:
> where i can read more about this (I mean the development of custom
> ICAP/eCAP modules and their connection to the proxy) ?
The best place to start is probably
https://wiki.squid-cache.org/SquidFaq/ContentAdaptation
If you decide to go the ICAP route, you will need to find the right ICAP
server for your project. After that, the development will revolve around
writing a custom adapter for that ICAP server. The above URL links to a
page with a list of ICAP servers:
https://wiki.squid-cache.org/Features/ICAP
If you decide to go the eCAP route, you will need to (find somebody to)
write an eCAP adapter (no server required).
In either case, the required development is similar to writing a plugin
or loadable module. Any capable developer can do it, but understanding
of HTTP concepts and familiarity with the ICAP server or eCAP API helps.
HTH,
Alex.
> >> 2018-06-13 12:54 GMT+03:00 Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx <mailto:uhlar@xxxxxxxxxxx>>:
> 2018-06-13 18:35 GMT+03:00 Alex Rousskov:
>
> 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".
>
>
> >>
> >>> 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.
>
>
> _______________________________________________ > <mailto:squid-users@lists.
> squid-users mailing list
> squid-users@lists.squid-cache.org
squid-cache.org >
> http://lists.squid-cache.org/listinfo/squid-users
> <http://lists.squid-cache.org/listinfo/squid-users >
>
>
>
>
> --
> With best regards,
>
> Vyacheslav Yakushev,
>
> Unix system administrator
>
> https://t.me/kelewind
With best regards,
Vyacheslav Yakushev,
Unix system administrator
https://t.me/kelewind
Vyacheslav Yakushev,
Unix system administrator
https://t.me/kelewind
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
