Skip to content

400 when content header contains charset #93

@madevoge

Description

@madevoge

Some clients add a charset to the content header:
application/json;charset=UTF-8

This breaks the full equals check here:

The following makes the equals check a bit more flexible, allowing charsets
ct.content != ContentType.Application.Json.content

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions