In order to move to the more secure auth methods usually requires a
config setting in the LDAP to enable support for secure
authentication
tokens instead of a password. If you are lucky the LDAP server
already
has that turned on and you only need to add other authentication LDAP
helpers
Hello List,
i am running Squid 3.1.0.14 and when i try to access
www.allplanlernen.de i get a 502 error. It works without squid.
Does anyone know why?
Thanks,
Mario
Hallo, Mario,
Du meintest am 28.12.11:
i am running Squid 3.1.0.14 and when i try to access
www.allplanlernen.de i get a 502 error.
Same here (squid 3.2.0.14):
502 Bad Gateway
nginx/0.7.67
It works without squid.
Same here, too.
Does anyone know why?
Seems to be a
On 28/12/2011 17:58, Helmut Hullen wrote:
Works on squid 3.2.0.8
Eliezer
Hallo, Mario,
Du meintest am 28.12.11:
i am running Squid 3.1.0.14 and when i try to access
www.allplanlernen.de i get a 502 error.
Same here (squid 3.2.0.14):
502 Bad Gateway
nginx/0.7.67
It
Brett Lymn brett.l...@baesystems.com wrote in message
news:20111228062759.gb21...@baea.com.au...
On Wed, Dec 28, 2011 at 05:23:55PM +1100, James Robertson wrote:
Because I implemented Kerberos first I already had a machine account
in Active Directory that was created by the msktutil utility.
Consider the following configuration lines
https_port 443 cert=/etc/apache2/certs/server.pem
key=/etc/apache2/certs/server.key vhost vport
cache_peer 127.0.0.1 parent 8443 0 ssl no-query originserver
sslflags=DONT_VERIFY_PEER front-end-https login=PASS
What if there is more site ssl sites which
Hi Roman,
What version of Squid are you using ?
Cheers,
Pieter
On Wed, 28 Dec 2011, Roman Gelfand wrote:
Consider the following configuration lines
https_port 443 cert=/etc/apache2/certs/server.pem
key=/etc/apache2/certs/server.key vhost vport
cache_peer 127.0.0.1 parent 8443 0 ssl
version 3.16.
On Wed, Dec 28, 2011 at 1:21 PM, Pieter De Wit pie...@insync.za.net wrote:
Hi Roman,
What version of Squid are you using ?
Cheers,
Pieter
On Wed, 28 Dec 2011, Roman Gelfand wrote:
Consider the following configuration lines
https_port 443
Hallo, Mario,
Du meintest am 28.12.11:
i am running Squid 3.1.0.14 and when i try to access
www.allplanlernen.de i get a 502 error.
Same here (squid 3.2.0.14):
502 Bad Gateway
nginx/0.7.67
It works without squid.
Same here, too.
Does anyone know why?
Seems to be a
It's working fine in squid 3.1.18 with google chrome 16.0.912.63 m and
IE 9.0.8112.16421
On 28/12/2011 22:26, ml ml wrote:
Hello List,
i am running Squid 3.1.0.14 and when i try to access
www.allplanlernen.de i get a 502 error. It works without squid.
Does anyone know why?
Thanks,
On 28/12/2011 10:45 p.m., FredB wrote:
In order to move to the more secure auth methods usually requires a
config setting in the LDAP to enable support for secure
authentication
tokens instead of a password. If you are lucky the LDAP server
already
has that turned on and you only need to add
On 28/12/2011 3:19 p.m., Ming Pun wrote:
Thanks for the prompt response. It is very useful. I was playing
external_acl_type to understand how it works.
a couple of questions
- when a request did not pass external acl , I got a HTTP 403. How
can I make it to return 401 instead?
That is
I just had one of my webservers go down, unrelated to my squid server on
my local lan, but I noticed that after a certain ammount of time, seems
that once squid realizes that a host is down it will then serve the
most recent version of the site from cache, which I think is EXCELLENT,
i never
On Wed, 28 Dec 2011 22:17:43 -0800, someone wrote:
I just had one of my webservers go down, unrelated to my squid server
on
my local lan, but I noticed that after a certain ammount of time,
seems
that once squid realizes that a host is down it will then serve the
most recent version of the
14 matches
Mail list logo
