Hello again Henrik,
To be exact, I also have to remove %DST to realize what I expect.
If %DST remains, the helper is still called every time the user
accesses different hosts...
Thanks again.
Regards,
Norio
> Henrik,
>
> Thank you so much! Your answer did help me a lot and I could
> understand what the problem was! As you advised, I could solve
> the problem by removing %{Referer} from the external_acl_type
> statement below.
>
> In fact, I just added %{Referer} and some other arguments to
> leave them as logs of the helper...
>
> Thanks again.
> Regards,
> Norio
>
>
> > On Mon, 31 Jan 2005, Norio Korekawa wrote:
> >
> > > external_acl_type myacltype %LOGIN %SRC %DST %{Referer} %{User-Agent} /usr/lib/squid/myaclhelper.pl
> > > acl myacl external myacltype
> >
> > > It seems that myaclhelper.pl is called by squid, every time new URL
> > > is accessed, but is this correct action?
> >
> > To be precise the helper is called for every new unique combination of the
> > arguments
> >
> > %LOGIN %SRC %DST %{Referer} %{User-Agent}
> >
> > As you include Referer this means that the helper will be called pretty
> > much for every unique link your users click on or otherwise implicitly
> > accesses (including each inlined objects) during the ttl.
> >
> > The helper is called for every unique combination of the arguments sent to
> > it.
> >
> > so it's not exacly each link.. but I think you get the picture if you look
> > at the arguments
> >
> > If you limit yourself to not sent %{Referer} then the helper will be
> > called for every unique site each user visits, or twice if the user uses
> > two different web browsers.
> >
> > > I think my squid.conf has some problems, but I don't know what they are...
> >
> > More likely a slight misunderstanding on how the external_acl helpers
> > work, or what is included in the Referer and/or User-Agent HTTP headers.
> >
> > Regards
> > Henrik
