W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re: Semantics of HTTPS

From: Mike Belshe <mike@belshe.com>
Date: Mon, 6 Aug 2012 16:07:20 -0700
Message-ID: <CABaLYCvcepmX0=zYp_GBXG9NzKG_PLEq5X_AUgC+gs3rwtevmg@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On Mon, Aug 6, 2012 at 1:32 PM, Mark Nottingham <mnot@mnot.net> wrote:

> <
> https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p1-messaging.html#https.uri>
> is slated to define the semantics of HTTPS urls.
>
> We currently talk about HTTPS' impact on caches and identity there, but we
> don't mention one other major effect on HTTP -- the use of CONNECT to
> proxies.
>
> I think we need to define HTTPS as having a semantic of *end-to-end* use
> of SSL/TLS, and therefore CONNECT to proxies.
>

+1.  I don't think we can take away https' end-to-end properties
retroactively.

Mike


>
> Make sense?
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>
>
>
>
>
Received on Monday, 6 August 2012 23:07:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 August 2012 23:07:54 GMT