Subject: [httpwg/http-extensions] How to handle non-canonical base64? (#473)

From: HTTP issue updates <[email-masked]>
Date: Fri, 19 Jan 2018 19:17:03 +0000 (UTC)

http://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html#binary says to 
> Let binary_content be the result of Base 64 Decoding [RFC4648] b64_content, synthesising padding if necessary.

However, https://tools.ietf.org/html/rfc4648#section-3.5 says
> decoders MAY chose to reject an encoding if the pad bits have not been set to zero.

Structured headers should specify whether to reject these encodings. For example, do both `iZ` and `iQ` decode to 0x89 or is `iZ` an error?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/473