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

Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea

From: Grahame Grieve <grahame@kestral.com.au>
Date: Wed, 18 Jul 2012 14:20:46 +1000
Message-ID: <CAG47hGYP8OVqUbgxUZx=FO-BmbDM_4B6OeQtb0jmBi+R5RECOg@mail.gmail.com>
To: Mike Belshe <mike@belshe.com>
Cc: "Adrien W. de Croy" <adrien@qbik.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

> Can you enumerate these?  For debugging, of course it makes sense for
> endpoints to have unencrypted modes.

oh? but it was going to be mandatory. Except when it's not? which is it?
If it's mandatory by policy, but not technically actually required,
then... well..
I think I know how that will turn out.

Grahame

Received on Wednesday, 18 July 2012 04:21:14 GMT

This message: [ Message body ]
Next message: Mike Belshe: "Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea"
Previous message: Mike Belshe: "Re: HTTP2 Expression of Interest"
In reply to: Mike Belshe: "Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea"
Next in thread: Mike Belshe: "Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea"
Reply: Mike Belshe: "Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 18 July 2012 04:21:20 GMT