W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2015

Re: Call for Adoption: Encrypted Content Encoding

From: Walter H. <Walter.H@mathemainzel.info>
Date: Wed, 02 Dec 2015 12:48:22 +0100
Message-ID: <565EDA86.80909@mathemainzel.info>
To: Cory Benfield <cory@lukasa.co.uk>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 01.12.2015 12:05, Cory Benfield wrote:
> Sorry, I’m still perplexed by this. If a server is worried about allowing unvalidated binary data through, that server should send 415 Unsupported Media Type in response to any request with Content-Encoding: aesgcm128.

refusing Content-Encoding: aesgcm128 for invalid or bad data, e.g. 
malware means also refusing Content-Encoding: aesgcm128 for valid or 
good data ...

any Webadmin should think of the fact, that he/she can be made 
responsible for spreading malware ...

  which sense does this draft then have?



Received on Wednesday, 2 December 2015 11:48:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:40 UTC