On 1/7/22 4:39 PM, Graminsta wrote:
> I thought it was filtered by you guys before make it public.
> Other sensitive content I sent was erased before it came in this list.
Just to avoid misunderstanding: squid-users emails from subscribers are
not moderated by default. Content erasure, if any, is
On Friday 07 January 2022 at 22:39:41, Graminsta wrote:
> Now I have to change the pw of about 200 VPSs, hell.
I have to question the wisdom of using the same root PW on multiple servers,
even when that PW has not been posted on a public mailing list.
Antony.
--
I bought a book on memory tec
I I thought it was filtered by you guys before make it public.
Other sensitive content I sent was erased before it came in this list.
Its to bad.
Now I have to change the pw of about 200 VPSs, hell.
Marcelo Rodrigo
De: Bruno de Paula Larini [mailto:bruno.lar...@riosoft.com.br]
Enviada em:
Hello :)
I have a specific problem with facebook access in squid 4.13 with Ubuntu 20.
It can access all other IPV6 websites but not https://www.facebook.com. Or
any other facebook URL.
Outside of squid, the access is working via curl in the same server with the
same IPV6 addresses.
It hap
On 1/7/22 12:12 AM, Praveen Ponakanti wrote:
> Is there a build with the fix, or do you have some recommended steps
> to manually pull the source, patch the fix and then recompile?
Yes, applying the patch to official Squid sources and then bootstrapping
and building from patched sources is what f
On 1/7/22 9:34 AM, Amos Jeffries wrote:
> On 7/01/22 06:00, Alex Rousskov wrote:
>> On 1/6/22 6:53 AM, Majed Zouhairy wrote:
>>> after upgrading today to 5.3 i'm getting:
>>
>>> 2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
>>> exception location: FwdState.cc(628) noteDestinationsEn
On 7/01/22 06:00, Alex Rousskov wrote:
On 1/6/22 6:53 AM, Majed Zouhairy wrote:
peace i have squid with ufdb guard, after upgrading today to 5.3 i'm
getting:
2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
exception location: FwdState.cc(628) noteDestinationsEnd
what is the c
> > I cannot answer for Amos who asked for those logs, but you may want to
> > try a fix posted at
> > https://bugs.squid-cache.org/show_bug.cgi?id=5132#c27
> >
> >
>
> If that does not work the data you have collected may still be useful to
> figure out what exactly is hitting you.
Update (che
On 7/01/22 17:16, Alex Rousskov wrote:
On 1/6/22 2:50 AM, Praveen Ponakanti wrote:
Hi Alex/Amos,
Do you still need memory logs from version 5.3 after stopping traffic
through the squid?
I asked so anyone taking on the bug would have data to work with. 3 days
worth should be plenty to work
On 7/01/22 06:26, Grant Taylor wrote:
On 1/4/22 9:56 AM, Will BMD wrote:
I'm not aware of WCCP, but I'll look into it.
In short, the Web Cache Communications Protocol, "... specifies
interactions between one or more routers (or Layer 3 switches) and one
or more web-caches ...".
Link - Web
FYI people,
When Squid
On 7/01/22 06:33, Grant Taylor wrote:
On 1/4/22 2:35 AM, Will BMD wrote:
HTTP proxy limitation
The system cannot decrypt traffic if an HTTP proxy is positioned
between a client and your managed device, and the client and server
establish a tunneled TLS/SSL connection
11 matches
Mail list logo
