- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 13 Oct 2021 14:52:22 +0200
- To: ietf-http-wg@w3.org
Am 13.10.2021 um 08:56 schrieb Carsten Bormann: > On 2021-10-13, at 08:48, Julian Reschke <julian.reschke@gmx.de> wrote: >> >> Am 12.10.2021 um 23:48 schrieb Carsten Bormann: >>> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-semantics-11 >>> says: >>> >>> media-type = type "/" subtype parameters >>> parameters = *( OWS ";" OWS [ parameter ] ) >>> >>> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-semantics-10 >>> says: >>> >>> media-type = type "/" subtype *( OWS ";" OWS parameter ) >>> >>> Is the rationale for making the parameter optional documented? >>> >>> Where -10 would have allowed: >>> text/plain;format=flowed >>> … 11 now allows: >>> text/plain;;;;format=flowed;; >>> >>> Very curious. >> >> See <https://github.com/httpwg/http-core/issues/33>. > > Thank you! > So my conclusion is that this is on the same level as OWS or obs-text and should not be promoted in new specifications using this syntax. I would characterize it as something that many implementations decided to accept despite it being invalid, and thus it got used in the wild. Disallowing it at this point was somewhat pointless. Not sure about what new specifications you have in mind. If it really replicates Content-Type syntax, I would just align with the current spec. On the other hand, if it's something really new, I would suggest looking at Structured Fields. Best regards, Julian
Received on Wednesday, 13 October 2021 12:52:34 UTC