On 6/10/23 06:15, Ludovit Koren wrote:
Amos Jeffries writes:
> On 5/10/23 19:30, Ludovit Koren wrote:
>> Hello,
>> I am using squid 5.9 with AD Kerberos authentication and could not
>> solve
>> the problem of sending incorrect request according to client
>>
On 10/10/23 22:23, Ludovit Koren wrote:
Hi,
I am sorry to bother you once again, but I sent you and described just
the problem you were talking about and did not get any answer.
Sorry about that. Following up on the original thread in a short while.
PS. Normally no answer means nobody
Hi,
I am sorry to bother you once again, but I sent you and described just
the problem you were talking about and did not get any answer.
In the logged output you can see several 407 and afterwards 200 error
code just as you described, that the state you worry about.
Is there any solution to
> Amos Jeffries writes:
> On 5/10/23 19:30, Ludovit Koren wrote:
>> Hello,
>> I am using squid 5.9 with AD Kerberos authentication and could not
>> solve
>> the problem of sending incorrect request according to client
>> configuration followed by the correct one,
On 5/10/23 19:30, Ludovit Koren wrote:
Hello,
I am using squid 5.9 with AD Kerberos authentication and could not solve
the problem of sending incorrect request according to client
configuration followed by the correct one, i.e.:
1695983264.808 0 x.y.z TCP_DENIED/407 4135 CONNECT
Hello,
I am using squid 5.9 with AD Kerberos authentication and could not solve
the problem of sending incorrect request according to client
configuration followed by the correct one, i.e.:
1695983264.808 0 x.y.z TCP_DENIED/407 4135 CONNECT th.bing.com:443 -
HIER_NONE/- text/html
