Hello Squid Users
I am in need of some help. I believe this must have been done by some
already but i could not just get the right document to understand
well.
Setup :
Squid v3.2.3 on a RHEL 6 64-bit VM (say server1)
Apache's 2.2.15 on RHEL6 64-bit VM's (running in server1 and in server2).
Requ
Hi Amox, Thanks so much for helping out... Here are my replies ..
On Mon, Feb 4, 2013 at 1:39 PM, Amos Jeffries wrote:
> On 4/02/2013 8:22 p.m., PARAM KRISH wrote:
>>
>> Hello Squid Users
>>
>> I am in need of some help. I believe this must have been done by some
>
Hi, Just to update , it worked fine. The problem was with the redirect
login cgi that had some permission issues in other server hence it did
not failover earlier. It now listens only in 443, works beautifully.
Thanks Amos for your help.
On Wed, Feb 6, 2013 at 10:16 AM, paramkrish wrote:
> Dear S
Hello
I have the squid running at port80 with the cache_peer on 443
I see there is only TCP_MISS/200 or TCP_MISS_ABORTED/200, I doubt
whether Squid is really caching of the pages.
1368334462 000179 10.56.101.197 TCP_MISS/200 4621 GET
http://wikid-dev.eng.domain.com/ - SOURCEHASH_PARENT/engwikiwe
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 forwar
Thanks Amos. We are already on a Production, cant really think about
upgrading without knowing the impact and benefits, for now.
On the other hand, i picked up the "TCP_HIT" from my production box
that is a lot used, seem to have many there.
1368107093 00 10.56.9.27 TCP_HIT/200 738 GET
http:/
