That should have read:
>cache_peer parent 8080 7 no-digest no-query no-netdb-exchange default
>login=username:password name=proxy
>cache_peer parent 443 7 no-digest no-query no-netdb-exchange default
>login=username:password name=proxyssl
Apologies for that.
Gareth
On Tue May 8 13:18 , "[
Just seems odd.
I have put in the following
cache_peer parent 8080 7 no-digest no-query
no-netdb-exchange default
login=: name=proxy
cache_peer parent 443 7 no-digest no-query
no-netdb-exchange default
login=: name=proxyssl
and then further down:
cache_peer_access proxyssl allow CONNECT
c
[EMAIL PROTECTED] wrote:
Hi Chris,
Okay - I've followed those instructions and squid reloads the configuration file without any
issues.
After setting up a test machine, and looking through the archives of
this thread, it appears as though my instructions were... Less than
perfect. No su
[EMAIL PROTECTED] wrote:
Hi Chris,
Okay - I've followed those instructions and squid reloads the configuration file without any
issues.
To be clear, you are using the same domain name or IP address in both
definitions of the parent proxy, correct? You are no longer using the
"real" doma
Hi Chris,
Okay - I've followed those instructions and squid reloads the configuration
file without any
issues.
Browsing on port 8080 works, but once again 443 is challenging me for my
credentials even though I
have turned off all authentication.
The thing about squid is, it is selecting the
Gareth Edmondson wrote:
Hi Amos
Thanks for that. The lines are as follows:
#TAG: cache_peer_access
cache_peer_access proxyssl allow CONNECT
cache_peer_access proxyssl deny all
cache_peer_access deny CONNECT
cache_peer_access allow all
As for the cache_peer lines they are as follows:
#TAG: c
Hi Amos
Thanks for that. The lines are as follows:
#TAG: cache_peer_access
cache_peer_access proxyssl allow CONNECT
cache_peer_access proxyssl deny all
cache_peer_access deny CONNECT
cache_peer_access allow all
As for the cache_peer lines they are as follows:
#TAG: cache_peer
cache_peer par
Gareth Edmondson wrote:
Henrik Nordstrom wrote:
tis 2007-05-01 klockan 23:41 +0100 skrev Gareth Edmondson:
Thanks for the advice here. I read about this name= option earlier in
the archives - but I got the impression from previous posters that it
was in version 3 of squid and not the stable
Henrik Nordstrom wrote:
tis 2007-05-01 klockan 23:41 +0100 skrev Gareth Edmondson:
Thanks for the advice here. I read about this name= option earlier in
the archives - but I got the impression from previous posters that it
was in version 3 of squid and not the stable version that ships with
tis 2007-05-01 klockan 23:41 +0100 skrev Gareth Edmondson:
> Thanks for the advice here. I read about this name= option earlier in
> the archives - but I got the impression from previous posters that it
> was in version 3 of squid and not the stable version that ships with
> Debian Etch. The st
hi Henrik - answers inline...
Henrik Nordstrom wrote:
tis 2007-05-01 klockan 22:49 +0100 skrev Gareth Edmondson:
Now this threw up an error along the lines of having two cache_peer
names the same. So we edited the hosts file in DNS setting a name to
resolve to the same IP address. The lin
tis 2007-05-01 klockan 22:49 +0100 skrev Gareth Edmondson:
> Now this threw up an error along the lines of having two cache_peer
> names the same. So we edited the hosts file in DNS setting a name to
> resolve to the same IP address. The line now reads:
>
> cache_peer sslproxy 443 parent 7
T
Hi,
After searching the archives, I've decided to ask here.
We have setup a Debian Etch box which uses squid to access an upstream
proxy run by the education authority. They have given us a username and
password and it all works on port 8080 (after challenging us for our
Active Directory user
13 matches
Mail list logo
