Re: Call for Adoption: Encrypted Content Encoding

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?