Hi,
Sorry for my poor English. I think maybe I have figure out how to do this.
Seems I need to explicitly specific allow “google” for “my_auth” users.
Add this:
http_access allow google my_auth
before
http_access allow my_authall
auth_para
Hi,
*
**"Access to google maps(https://www.google.com/maps) should prevent any
authentication need"*
I could understand that all users should be able to access the google
maps link without any authentication. For this you could add the site
acl before the authentication part in the squid conf
Does it exist guideline to tune up/down cache_dir size?
What do you think about use of ram disk as cache_dir vs hard disk ?
On 06 Nov 2014, at 10:16, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 6/11/2014 8:58 p.m., Riccardo Castellani wrote:
>> I'm installing n
Hello all,
As our company policy only allow some machines to access to some SSL website
URL(eg. https://www.google.com/maps). However, they do not have access to
https://www.google.com/ Before, we tried to implement authentication,
everything works fine. We try to allow https access to
https://
Bumping this with another backtrace. Happened at 16:05 this time, when the
system was not very very busy.
It’s causing squid to crash in such a way that I actually have to `kill -9` the
process in order to get things restarted properly.
Would really appreciate any feedback at all from any
> Sent: Wednesday, November 05, 2014 at 10:48 PM
> From: "Amos Jeffries"
> On 6/11/2014 2:33 p.m., doc.holli...@usa.com wrote:
>>
>> I've searched through the internets and tried various things... to
>> no avail. Hopefully someone here can point me in the right
>> direction. I am sitting behind
Victor Sudakov wrote:
>
> However, I am eager to know what could be causing such weird tickets
> to be issued, but I think only a Windows expert can tell. After all,
> the key in the tickets is correct, only the principal name is changed.
> I only suspect that the name is changed when the client s
Hi
After migration from squid 3.3.13 to 3.4.4, I recognized a
performance-issue. Squid is configured with 4 workers. They often have
a CPU-Utilization between 50%-90% (each worker). With squid 3.3.13
(same configuration), the CPU-Utilization was never a problem. I
installed squid 3.4.9 and had the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/05/2014 11:56 AM, Odhiambo Washington wrote:
> Hi Eliezer,
>
> That link should be fine, although my system is actually PC-BSD.
> The version is the same though an old version. My exact version
> is:
> ftp://ftp.pcbsd.org/pub/archived/9.1-RELEA
Thank You.
Now I understand.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-tp4668210p4668231.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mailing list
squid-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 9:45 p.m., navari.lorenzo wrote:
> hello boys, excuse my bad english
>
> there is something i don't understand. If i write an URL into a
> browser which use Squid (for example www.xxx.com) (denied whith an
> acl)
>
> I expect that Squid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 8:58 p.m., Riccardo Castellani wrote:
> I'm installing new machine as Squid server and I need to understand
> what criteria to estimate the 'cache size', I'm not speaking about
> extra space for swap/temporary files or fragmentation but I'
hello boys,
excuse my bad english
there is something i don't understand.
If i write an URL into a browser which use Squid (for example www.xxx.com)
(denied whith an acl)
I expect that Squid answer saying: you cannot access this url because it is
a denied url.
This should happen without squid goe
13 matches
Mail list logo
