Hello James,
Here is to confirm that after applying this patch, rebuilding Squid 4.6 and
deploying it into production of about 700 proxy connected clients using mostly
Kerberos authentication followed by NTLM and Basic LDAP the mentioned issue
with negotiate wrapper went away. No more pop us
On 7/15/19 7:54 PM, James Zuelow wrote:
>> On 7/15/19 3:11 PM, James Zuelow wrote:
>>
>>> how could I go about confirming the presence of bug 4936 in the
>>> current Debian stable version of Squid?
>>
>> If you want to be sure, get the source code version of the Debian Squid
>> package (with all
On 7/15/19 7:46 PM, Lei Wen wrote:
> Does request_header_replace support calling another file
No, AFACIT, request_header_replace's replacement value does not support
dynamic evaluation of any kind (such as logformat %code expansion). One
should be able to use an eCAP service, an ICAP service, and
> On 7/15/19 3:11 PM, James Zuelow wrote:
>
> > how could I go about confirming the presence of bug 4936 in the
> > current Debian stable version of Squid?
>
> If you want to be sure, get the source code version of the Debian Squid
> package (with all the Debian patches applied) and check
I am using request_header_replace to modify out going HTTP headers, mainly
the basic/bearer token. Does request_header_replace support calling another
file, the content in that file would be "Basic ...".
Thanks,
Lei
___
squid-users mailing list
On 7/15/19 4:50 PM, --Ahmad-- wrote:
> i ask is it possible we have it as variable ?
>
> and tcp_outgoing_address to match acl as variable header from incoming
> packs ?
Sorry, I do not understand what "as variable" means in this context.
Please give an example or explain why the proposed
On 7/15/19 3:11 PM, James Zuelow wrote:
> how could I go about confirming the presence of bug 4936 in the
> current Debian stable version of Squid?
If you want to be sure, get the source code version of the Debian Squid
package (with all the Debian patches applied) and check whether
Hi Alex Thank you very much .
i ask is it possible we have it as variable ?
and tcp_outgoing_address to match acl as variable header from incoming packs ?
> On 15 Jul 2019, at 22:00, Alex Rousskov
> wrote:
>
> acl requestsWithStartEqual1p1p1p1 req_header Start ^1[.]1[.]1[.]1$
> ...
>
We have a pair of Squid proxies, running as a failover pair with ucarp.
Both of these proxies are domain joined with Samba, and we've been using
Kerberos authentication for several years.
After Debian Buster was released, we upgraded the failover unit and did some
basic testing. Everything
On 7/15/19 10:33 AM, --Ahmad-- wrote:
> i want to ask how can i adapt external ip address in squid based on incoming
> requests .
>
> say i have squid with ips :
> 1.1.1.1
> 2.2.2.2
> 3.3.3.3
> client will initiate a header called start with value = 1.1.1.1
> how can i let squid make
Hello Team .
i want to ask how can i adapt external ip address in squid based on incoming
requests .
say i have squid with ips :
1.1.1.1
2.2.2.2
3.3.3.3
##
a client with src ip 192.168.1.200 will connect to squid port 3128 .
client will initiate a header called start with
Alex,
>The feature has already been rejected from the official v4 inclusion
>because the underlying changes are too big/risky for that branch.
I see. I understood that the v4 won't be able to support it.
Anyway, when will you release v5 officially ?
Regards,
--
Mikio Kishi
On Mon, Jul 15, 2019
On 15.07.19 14:28, Nurdiyana Ali wrote:
We have Squid Cache: Version 3.5.20 deployment in our environment. Our
users require access to web.whatapp.com. I whitelisted this site on the
proxy configuration
how? can you show us the directive you have used to allow access to
whatsapp?
, however,
Hello,
We have Squid Cache: Version 3.5.20 deployment in our environment. Our
users require access to web.whatapp.com. I whitelisted this site on the
proxy configuration, however, it's giving out error:
Can’t connect securely to this page
This might be because the site uses outdated or unsafe TLS
14 matches
Mail list logo
