Normally Suqid sends a ICP query on each and every cache miss request
(not just page.. there is no such thing as "page" in HTTP).
If squid thinks your application is dead then it will stop sending ICP
queries for a short while to not waste bandwidth. A peer is declared
dead if no valid ICP responses have been received after a timeout.. In
such case the event is logged in cache.log.
Other cause may be the fact that peers is only used for hierarchical
requests. Meaning that any requests which either matches
hierarchy_stoplist or is using a uncacheable HTTP method will by default
go directly to the origin server, bypassing any cache_peer options.
Regards
Henrik
Emmanuel Duros wrote:
>
> Hi,
>
> I am writing an application that listens to ICP Queries from squid. Upon
> reception of the query the application replies with an ICP_MISS
> pkt. Then my application asks for the URL contained in the Query and
> does some processing on the page...
>
> I use a browser that connects to squid to surf the web. I would expect
> squid to always send ICP queries to my application for pages/objects
> that are not in the cache. However I can notice that quite often squid
> does not send ICP query for missing pages.
>
> My feeling is that I have to wait for a few seconds between clicks on
> html links in order to always get the ICP query from squid.
>
> Is there anything I can do to force squid to always send ICP queries ???
>
> Thanks,
> Emmanuel
Received on Wed Jan 29 2003 - 16:01:24 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:12:58 MST