On 2016-03-24 13:41, Markey, Bruce wrote:
I'm hoping this is a simple question, I've gotten/seen differing
answers and I'd just like a final answer.
With squid setup as a transparent proxy via wccp will there be any log
entries for https sites, even just the ip? Just the initial get
request is
I'm hoping this is a simple question, I've gotten/seen differing answers and
I'd just like a final answer.
With squid setup as a transparent proxy via wccp will there be any log entries
for https sites, even just the ip? Just the initial get request is what I'd
expect.
( I have no interest in
> -Original Message-
> From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On
> Behalf Of Amos Jeffries
> Sent: Wednesday, March 23, 2016 11:50 PM
> To: squid-users@lists.squid-cache.org
> Cc: 819...@bugs.debian.org
> Subject: Re: [squid-users] Negotiate wrappter returns
On 25/03/2016 1:24 a.m., Luis Daniel Lucio Quiroz wrote:
> I understand, buggy I really need to take out this sniproxy in favor of
> squid.
>
> I'm planning that this path needs the HTTP violation flag on compile time,
> and by default value is off. So when turning on, it won't be an accident.
>
I understand, buggy I really need to take out this sniproxy in favor of
squid.
I'm planning that this path needs the HTTP violation flag on compile time,
and by default value is off. So when turning on, it won't be an accident.
Host_verify_header would be a good name for this on/off option
Le 24
On 24/03/2016 4:11 a.m., Yuri Voinov wrote:
>
> i.e., for example,
>
> request_header_access Cache-Control deny all
> request_header_access Cache-Control: max-age=0
Only alters the *outbound* from Squid to server.
>
> will raise cache hit ratio in conjunction with reload_into_ims on, right?
>
On 24/03/2016 11:17 p.m., L.P.H. van Belle wrote:
> Hai Amos,
>
> Thank you, very appriciated, one question more, if i did understand it
> correctly.
>
> When using the wrapper helpers, and wanting only kerberos auth.
>
Do not use the wrapper when wanting only one of the flavours of
Negotia
Hai Amos,
Thank you, very appriciated, one question more, if i did understand it
correctly.
When using the wrapper helpers, and wanting only kerberos auth.
Then this is correct?
(Sorry to ask, but i have to translating things, and its not always clear.)
auth_param negotiate program /usr/l
On 24/03/2016 10:08 p.m., L.P.H. van Belle wrote:
> Hello Amos,
>
> I was missing in my setup also, now i know the problem where that was comming
> from. Can you help me a bit with explaining the diffence in these base on
> below example. Because if i post somewhere, i want to be sure the setup
Hello Amos,
I was missing in my setup also, now i know the problem where that was comming
from. Can you help me a bit with explaining the diffence in these base on below
example. Because if i post somewhere, i want to be sure the setup is correct.
And it was not, :-(, im thinking, what i misse
On 24/03/2016 3:56 p.m., Luis Daniel Lucio Quiroz wrote:
> As A side note, I am reading the code seems file
> src/client_side_request.cc function
> ClientRequestContext::hostHeaderVerify() is responsible for this.
>
> And to be exact this option:
> if (ia != NULL && ia->count > 0) {
>/
On 18/03/2016 7:29 a.m., James Zuelow wrote:
> Hello -
>
> I have Squid 3.4.8 installed on Debian Jessie.
>
> I'm using the negotiate wrapper configured like this:
>
> auth_param negotiate program /usr/lib/squid3/negotiate_wrapper_auth -d \
>--kerberos /usr/lib/squid3/negotiate_kerberos_auth
12 matches
Mail list logo
