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

Re: http+aes

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Mon, 5 Mar 2012 12:14:00 +0100
Cc: "Julian Reschke" <julian.reschke@gmx.de>, "Poul-Henning Kamp" <phk@phk.freebsd.dk>, "Willy Tarreau" <w@1wt.eu>, URI <uri@w3.org>, "HTTP Working Group" <ietf-http-wg@w3.org>, "Ian Hickson" <ian@hixie.ch>
Message-Id: <358C79F6-67F7-4F4A-95E6-186F8B37A653@greenbytes.de>
To: "Anne van Kesteren" <annevk@opera.com>
So the gist of http+aes is to URL-inject a Transfer-Encoding into the
existing http infrastructure?

//Stefan

Am 05.03.2012 um 12:08 schrieb Anne van Kesteren:

> On Mon, 05 Mar 2012 12:02:19 +0100, Julian Reschke <julian.reschke@gmx.de> wrote:
>> But yes, it's not entirely clear why this needs to be in the URL.
> 
> If you don't tie it to the URL, you will have to change every API (<a>, XMLHttpRequest, <video>, <script>, ...) to also take a key.
> 
> 
> -- 
> Anne van Kesteren
> http://annevankesteren.nl/
> 

<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Received on Monday, 5 March 2012 11:14:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:56 GMT