Andreas.Lamprecht@siemens.at writes:
>Hello!
>
>I ran into some problems with squid (1.1.x):
>
> - If using the hierarchy_stoplist, it works only for GET requests, not
>for
> POST, CONNECT and so on. Is there a reason for this ?
>
> What would you say to a "hierarchy_stoplist_pattern(/i)" directive
> which is honored by all request types (GET, POST, CONNECT ...).
This is basically due to some hueristics, which are semi-valid.
You may have noticed that in an ICP packet, there is no field for
the request method. From day one, it was assumed that only GET
requests would be cachable. All other request methods would
not be cachable, therefore no need to look for them in neighbor
caches, therefore no need to stick the request method in ICP.
So it is basically hard-coded into Squid that non-GET requests
will be handled directly, if possible.
And 'hierarchy_stoplist_pattern' already exists...
Duane W.
Received on Fri Jan 17 1997 - 10:04:10 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:34:06 MST