Skip to content

Check why UTF-8 decoding does not fail on illegal encodings of Surrogate codes #363

@cowtowncoder

Description

@cowtowncoder

See FasterXML/jackson-dataformats-binary#65 for background: it looks like UTF-8 json parser is not checking for case of 3-byte character being surrogate: I think it should.
(although there is still the whole issue of why JSON escapes may be used in such a way...).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions