Hi again, On 7/13/07, Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx> wrote:
fre 2007-07-13 klockan 12:13 -0400 skrev Mehr Faridpour: > Hi everybody, > > When my squid server accesses some pages it gets redirected (by my > isp) to some specific page saying I cannot access the requested page > (it is being filtered). Via a 3xx redirect?
Not any more, Actually in the last few days they changed the scheme of their filtering and now squidclient produce the following; (a bit edited by me) squidclient http://a_filtered_site HTTP/1.0 403 Forbidden X-Cache: MISS from my_squid_server X-Cache-Lookup: MISS from my_squid_server:3128 Proxy-Connection: close <HTML><HEAD><TITLE></TITLE> <META http-equiv=Content-Type content="text/html; charset=utf-8"> <BODY><P> </P> <P> </P> Their message here that the site is filtered .... </P></BODY></HTML>
> However I have a peer_cache that my squid > server could get any page I like via this peer_cache (it by passes the > filtering). My question is this: How can I tell my squid server that > if I request a page and it ends up to the redirected page ( i.e. it is > filtered) then drop the redirected page and try to get the requested > page via peer_cache? You need to build a list of URLs you want to access but which are blocked by the ISP, and set up cache_peer + cache_peer_access + never_direct to have these routed via that other peer.
Thanks for the input. It can help me anyway one day. So while they changed the way they filter I don't have the problem I had anymore, b/c appearantly 403 code instruct squid to use the cache_peer. I am correct?
Regards Henrik
Thanks Shahriar
