Skip to content

Warn and repair invalid UTF-8 content #19

Description

@tadman

The API will reject API calls with invalid UTF-8 content with a 406 "Not Accepted" error, but this could be avoided by scrubbing the input before sending it.

There seems to be a way to do this using Buffer to force-encode things.

Metadata

Metadata

Assignees

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