Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Poorly handled Content-Type header values #154

Closed
martin-georgiev opened this issue Aug 3, 2019 · 0 comments
Closed

Poorly handled Content-Type header values #154

martin-georgiev opened this issue Aug 3, 2019 · 0 comments

Comments

@martin-georgiev
Copy link
Collaborator

Content-Type header values like application/json; charset=us-ascii have side effects during validation.

Both RequestValidator and ResponseValidator use the Content-Type header value when validating the schema body. However, both classes use the raw value. Thus they do not take into account RFC 822's part about further information being provided in this header (for example charset).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant