From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Update-Accelerator 3.0
Date: Wed, 06 Mar 2013 23:03:40 +0100 [thread overview]
Message-ID: <1362607420.1828.3.camel@hughes.tremer.info> (raw)
In-Reply-To: <CAEpw26XnNz3QfZskeE0E-ugKYZU9ArzKkejD6w2DU+fFqFhnrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Wed, 2013-03-06 at 21:02 +0100, Jan Behrens wrote:
> okay dynamic is not always really dynamic. Youtube-Videos are also
> dynamic content to squid.
> So is everything with ? in the URL threaded as dynamic in squid.
That's a bad decision if that is true, because having a query term does
not necessarily make content dynamic. There are things like the Expires:
and Pragma: headers in HTTP to control what has to be cached and for how
long.
> well it would be possible to cache HTTPS - Content with
> "Man-in-the-Middle" Squid.
> The client will make a HTTPS-connection to squid and squid will make
> it's connection to the original destination server. At this point
> squid can serve and save content.
Not with me. This heavily violates the concept of secure communication.
In my opinion, I cannot trust the proxy to correctly verify the server's
certificate for example. This is only one among a whole bunch of
security issues.
-Michael
next parent reply other threads:[~2013-03-06 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEpw26XnNz3QfZskeE0E-ugKYZU9ArzKkejD6w2DU+fFqFhnrw@mail.gmail.com>
2013-03-06 22:03 ` Michael Tremer [this message]
[not found] <CAAiW7AfumUceBaNypjgWy0bTpV6UWQvWYHg5N=5-CyfrNS6UDA@mail.gmail.com>
2013-03-05 12:50 ` Jörn-Ingo Weigert
2013-03-05 15:43 ` Michael Tremer
2013-03-05 15:53 ` Jörn-Ingo Weigert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1362607420.1828.3.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox