Hi
Have you tried to use a ACL based upon a type of list of:-
acl AlwaysDirectSites url_regex -i "/etc/squid3/alwaysdirectsites"
http_access allow AlwaysDirectSites
always_direct allow AlwaysDirectSites
Also as a safety measure, I would possibly use
cache_peer_access deny AlwaysDirectSites
to ensure these did not get passed to and Cache Peers.
This setup I use basically to prevent any sites listed in the file
"/etc/squid3/alwaysdirectsites" to be sent to a Cache Peer and to
always go out direct, and thus hopefully not have any filtering
issues.
This has got us around issues of some sites where they sometimes are
not Proxy friendly for some reason.
Thanks
Andy
On 20 October 2011 19:06, Ed W <lists_at_wildgooses.com> wrote:
> On 20/10/2011 06:11, Wilson Hernandez wrote:
>>
>> To tell you the truth I don't know whats the deal: bandwithd or squid
>> but, is really getting in my nerve loosing users left and right every
>> week.... I need to come up with a solution before my whole network
>> goes down the drain....
>>
>
> You need to get a reproducible situation and work from there. Find a
> tame user with the problem and get network timings, etc. Trace it on
> the server, setup direct access vs proxy access for them and compare
> performance, etc.
>
> You can use things like Chromes developer mode, or Firefox
> Firebug/Tamperdata to see network traffic and timings - that alone would
> probably help you a lot (pages can seem sluggish if certain assets such
> as javascript or css are slow to load and block page rendering - often
> these assets can be advertising things, or other things which might be
> handled differently in your proxying situation)
>
> Good luck
>
> Ed W
>
Received on Tue Oct 25 2011 - 20:47:19 MDT
This archive was generated by hypermail 2.2.0 : Wed Oct 26 2011 - 12:00:02 MDT