how to configure poxy cache server ?
i have these address ,gateway 172.24.0.3 and proxy ip address is ygncache.mptadsl.net.mm .my ISP gives DHCP ip address to us, so how can i confifure into the squid.conf . now i have configured like these http_port 192.168.11.1:9090 cache_mem 512 MB cache_dir ufs /usr/local/squid/var/cache 1 16 256 acl mynetwork 192.168.1.0/24 http_acces allow mynetwork cache_peer ygncache.mtpadsl.net.mm parent 8080 0 default-no query never_direct allow all but i cant access internet from my clients . so what configuration do i configure ? plz help me -- View this message in context: http://www.nabble.com/how-to-configure-poxy-cache-server---tp24047483p24047483.html Sent from the Squid - Development mailing list archive at Nabble.com.
Re: Problem with cached entries w/ETag and request without If-None-Match header
Selecting request headers are specified by Vary; If-None-Match is a conditional request header. Cheers, On 16/06/2009, at 12:44 AM, Jason Noble wrote: From RFC 2616 13.6: ... When the cache receives a subsequent request whose Request-URI specifies one or more cache entries including a Vary header field, the cache MUST NOT use such a cache entry to construct a response to the new request unless all of the selecting request-headers present in the new request match the corresponding stored request-headers in the original request. ... For the case in question, all selecting request headers do not match the stored request headers. Therefore, the cache must not use the stored entry to construct a response. --Jason Mark Nottingham wrote: What requirement in RFC2616 does this violate? On 13/06/2009, at 3:02 AM, Jason Noble wrote: I recently ran into a bug on Squid 2.7 regarding cached content with ETags. Currently, if all cached entries for a URL include ETags, and a request is received for said URL with no If-None- Match header, Squid will serve a cached entry. This behavior does not follow RFC 2616. I have attached a patch that prevents Squid from serving the cached entries in said case here: http://www.squid-cache.org/bugs/show_bug.cgi?id=2677 I would appreciate any feedback regarding this patch. Thanks, Jason -- Mark Nottingham m...@yahoo-inc.com -- Mark Nottingham m...@yahoo-inc.com
Re: Problem with cached entries w/ETag and request without If-None-Match header
From RFC 2616 13.6: ... When the cache receives a subsequent request whose Request-URI specifies one or more cache entries including a Vary header field, the cache MUST NOT use such a cache entry to construct a response to the new request unless all of the selecting request-headers present in the new request match the corresponding stored request-headers in the original request. ... For the case in question, all selecting request headers do not match the stored request headers. Therefore, the cache must not use the stored entry to construct a response. --Jason Mark Nottingham wrote: What requirement in RFC2616 does this violate? On 13/06/2009, at 3:02 AM, Jason Noble wrote: I recently ran into a bug on Squid 2.7 regarding cached content with ETags. Currently, if all cached entries for a URL include ETags, and a request is received for said URL with no If-None-Match header, Squid will serve a cached entry. This behavior does not follow RFC 2616. I have attached a patch that prevents Squid from serving the cached entries in said case here: http://www.squid-cache.org/bugs/show_bug.cgi?id=2677 I would appreciate any feedback regarding this patch. Thanks, Jason -- Mark Nottingham m...@yahoo-inc.com
