Skip to content

v3.x: Does the Encoding Object's contentType allow whitespace around commas? #4788

@handrews

Description

@handrews

I expected it would (e.g. contentType: text/css, text/javascript, image/*) by analogy with the Accept header, while @ralfhandl read it more literally and expects only contentType: text/css,text/javascript,image/* would be allowed. I suppose it depends on your assumptions on the phrase "comma-separated list" which is all we say about it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    clarificationrequests to clarify, but not change, part of the specmedia and encodingIssues regarding media type support and how to encode data (outside of query/path params)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions