> > My current guess looking at things around the package is that it is ok on my
> > build to have it in etc/squid, plus is a good place for a config file, so...
> > everything looks ok.
>
> Yes. It is supposed to be a config file to tell Squid where to load static
> web content from (based on
On 7/02/21 1:24 pm, Santiago Garcia Mantinan wrote:
On current build we ship usr/share/squid/mime.conf on squid-common, but on
my build it gets installed on etc/squid/mime.conf, which place is the right
one?
My current guess looking at things around the package is that it is ok on my
build to
> On current build we ship usr/share/squid/mime.conf on squid-common, but on
> my build it gets installed on etc/squid/mime.conf, which place is the right
> one?
My current guess looking at things around the package is that it is ok on my
build to have it in etc/squid, plus is a good place for a
Hi!
> There is also the GnuTLS ability to load multiple certificates for
> virtual-hosting HTTPS websites which OpenSSL simply cannot do itself. I
> know a few users are liking that.
I'm trying to make a double building like you suggested, but I don't think
we'll make it in time for Bullseye.
On Fri, 11 Dec 2020 08:10:02 +0100 Santiago Garcia Mantinan wrote:
For what I know, the openssl enabled binary will have all the features, it
is only that some options are gnutls specific, and this options are not
standard ones, I mean, the standard config or a normal cache usage doesn't
have
Hi!
I believe that would be messy for everybody, I think we should stick with
just one brand, otherwise people will find it harder to know what to
install.
For what I know, the openssl enabled binary will have all the features, it
is only that some options are gnutls specific, and this options
6 matches
Mail list logo
