"Linda A. Walsh" schreef:
Enough to verify what I am saying, usually, but I have expert
knowledge in almost no field that I know of.
Doesn't matter. All that matters is where you want to go and what you
need for that.
I have this feeling that I like SPDY better than HTTP2? Anyone agree?
Linda, Linda Walsh everywhere :p.
I only trashed your message. I love to trash Linda Walsh :P :P.
Okay, pointless message.
On Sun, 11 Oct 2015, Linda A. Walsh wrote:
The protocol usage in the 2nd case used 'http2' -- which started me
wondering what the heck that was...so googled around and
Again, impressed by your knowledge. But I'm not really arguing against
your knowledge. It is basically a principle choice to /call/ one thing
security and the other privacy based on the impression or experience that
the one thing provides actual defenses or benefits in certain common
scenario's
On Sun, 27 Sep 2015, Amos Jeffries wrote:
On 26/09/2015 11:48 p.m., Manuel wrote:
When Squid -even as a reverse proxy (which is my concern)- can not
retrieve the requested URL, it dicloses the IP address of the server
trying to contact with. Is there any way to hide that IP address to the
p
On 09/05/2015 02:22 PM, Rafael Akchurin wrote:
Hello Xen,
The certificate warning was most probably indeed caused by default SHA-1 signature of the
mimicked certificate in stock version of Squid present by default in popular Linux
distribs. Latest version does that correctly and your &quo
Hey,
Might I perhaps ask.
Currently with the default minimum configuration for ssl-bump that is
advocated everywhere, my Firefox bumping works but Chrome and Opera are
more strict and will say my certificate is invalid.
The certificate was simply generated (self-signed) with openssl x509
wi
I was assuming the files saved to the cache dir would just be plain
files as they were fetched. Am I mistaken? It seems weird that when I
run a 'file' on them, most of them are reported as "data" without
discrimination.
I remember from Squid 3.5 on Windows that I could take a file and open
it
Are you terribly certain the owner:group of the generated log files is
the same as those of the cache dirs?.
That is a way to check for sure what user it is running under. I was
just compiling the latest 3.5.x when it would complain, and I had
forgotten to compile it with --with-default-user=s
