Hi, Thanks for your reply. Here are my comments: squid.conf was sent earlier before you replied, you can go through and comment if that looks fine to you or has any issues in it. >Showing us the config would help answer that one. >Both squid.conf and a clear description of how the F5s are forwarding >traffic to Squid and how the squid box is receiving that traffic would >be a good start. Our domain wikid-dev.domain.com points to F5 VIP, which upon receiving the requests, does two things. 1) http to https redirection if received in https, 2) SSL Offloading, then forward the requests to Squid server @ 80. Squid config i had sent earlier which is believed to be forwarding the requests to two of its cache_peer to its port 443, and cacheing the pages as well. F5 and Squid setup what we have done is simple and straight forward, we have not done anything complex. Additionally, F5 uses OneConnect HTTP profile and has X_Forward enabled and i have kept SourceHash in the cache_peer in squid.conf to forward the requests to one cache_peer within the same TCP_connection to avoid any session related problems by blind round-robin. I will touch on this little later as i would still need to get my client_ip received from F5, which is not currently happening. But, right now i am worried about the cacheing that need to be addressed. >Why not? 443 and 80 are just ports. Both are just transferring TCP packets. When routing them there is no difference. Does it make a difference if F5 forward the requests to 443 or 80 to Squid ? I did that earlier but it never worked but if the cacheing problem is due to that, i can take your advice on this. -PK On Sun, May 12, 2013 at 12:34 PM, paramkrish <mkparam@xxxxxxxxx> wrote: > Additional info: > > Squid Cache: Version 3.2.3 > configure options: '--prefix=/usr/local/squid' '--enable-ssl' > '--enable-removal-policies=lru heap' '--enable-ltdl-convenience' > > squid.conf : > > cache_mgr enghelp@xxxxxxxxxx > cache_effective_user squid > cache_effective_group squid > > visible_hostname wikid-dev.domain.com > > http_port 80 accel defaultsite=wikid-dev.domain.com vhost > > cache_peer 10.56.102.92 parent 443 0 login=PASS name=engwikiweb1dev > sourcehash ssl sslflags=DONT_VERIFY_PEER > cache_peer 10.56.102.93 parent 443 0 login=PASS name=engwikiweb2dev > sourcehash ssl sslflags=DONT_VERIFY_PEER > > > acl wikid-dev dstdomain wikid-dev.domain.com > cache_peer_access engwikiweb1dev allow wikid-dev > #cache_peer_access engwikiweb2dev allow wikid-dev > cache_peer_access engwikiweb1dev allow all > #cache_peer_access engwikiweb2dev allow all > never_direct allow wikid-dev > > acl LUCENE url_regex lucene > cache deny LUCENE > > http_access allow wikid-dev > http_access allow all > > cache_replacement_policy heap LRU > memory_replacement_policy heap LRU > > cache_dir ufs /wikiweb-dev/squid-cache/var/engwikilb1/cache 2048 16 64 > > cache_swap_low 90 > cache_swap_high 95 > > cache_mem 1024 MB > maximum_object_size_in_memory 4096 KB > maximum_object_size 32768 KB > > logfile_rotate 3 > forwarded_for truncate > > cache_store_log /wikiweb-dev/squid-cache/var/engwikilb1/logs/cache_store.log > logformat squid %ts %06tr %>a %Ss/%03>Hs %<st %rm %ru %un %Sh/%<A %mt > > refresh_pattern -i \.css\?.*$ 1440 50% 2880 reload-into-ims > refresh_pattern -i \.js\?.*$ 1440 50% 2880 reload-into-ims > refresh_pattern -i \.css$ 1440 50% 2880 reload-into-ims > refresh_pattern -i \.js$ 1440 50% 2880 reload-into-ims > refresh_pattern (/skins/) 1440 50% 2880 reload-into-ims > refresh_pattern -i gen=css 1440 50% 2880 reload-into-ims > refresh_pattern -i gen=js 1440 50% 2880 reload-into-ims > refresh_pattern . 0 0% 0 > > > I would like if there is anything wrong in my config that makes not to cache > all the pages as i see only TCP_MISS statements in my access.log > > -PK > > > > -- > View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-not-caching-Please-help-tp4659918p4659924.html > Sent from the Squid - Users mailing list archive at Nabble.com.
