[squid-users] Re: adding content to the cache -- a revisit
[moving this to squid-users] When squid is talking to a cache_peer, is there a way to tell squid that if it gets a 404 back, to then send the request to the origin? Note that I currently have the cache_peer defined as a parent. Thanks Henrik Nordstrom wrote: mån 2009-10-12 klockan 07:57 -0600 skrev bergenp...@comcast.net: The content I'm trying to manually install into the squid server will be a subset of the origin server content, so for objects not manually installed into squid, squid will still need to go directly back to the origin server. What you need is a) A HTTP server on the Squid server capable of serving the objects using HTTP, preverably with as identical properties as possible as the origin. This includes at least properties such as ETag, Content-Type, Content-Language, Content-Encoding and Last-Modified. b) wget, squidclient or another simple HTTP client capable of requesting URLs from the proxy. c) cache_peer line telling Squid that this local http server exists d) A unique http_port bound on the loopback interface, only used for this purpose (simplifies next step) e) cache_peer_access + never_direct rules telling Squid to fetch content requested from the unique port defined in 'd' from the peer defined in 'c' and only then.. Regards Henrik
[squid-users] Re: adding content to the cache -- a revisit
ons 2009-10-28 klockan 11:22 -0600 skrev bergenp...@comcast.net: When squid is talking to a cache_peer, is there a way to tell squid that if it gets a 404 back, to then send the request to the origin? Not sure.. it may if you respond with 500, but not sure about 404.. And why do you need it to? Squid will go there on the first real request anyway. With the cache_peer_access rules this peer is only used on these automatic add content requests. Note that I currently have the cache_peer defined as a parent. What I intended. sibling is another option, but requires you to implement an ICP server. Regards Henrik
[squid-users] Re: adding content to the cache -- a revisit
Does sibling require ICP? I thought by setting the no-query option, ICP wasn't used to that cache_peer... ? Thanks Henrik Nordstrom wrote: ons 2009-10-28 klockan 11:22 -0600 skrev bergenp...@comcast.net: When squid is talking to a cache_peer, is there a way to tell squid that if it gets a 404 back, to then send the request to the origin? Not sure.. it may if you respond with 500, but not sure about 404.. And why do you need it to? Squid will go there on the first real request anyway. With the cache_peer_access rules this peer is only used on these automatic add content requests. Note that I currently have the cache_peer defined as a parent. What I intended. sibling is another option, but requires you to implement an ICP server. Regards Henrik
[squid-users] Re: adding content to the cache -- a revisit
ons 2009-10-28 klockan 16:13 -0600 skrev bergenp...@comcast.net: Does sibling require ICP? I thought by setting the no-query option, ICP wasn't used to that cache_peer... ? cache-digests also works.. it needs some means of knowing what content is held by the sibling, otherwise no requests will get forwarded there. REgards Henrik
