New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

slash #16

Open

kaffeeumeins opened this issue Mar 24, 2019 · 1 comment

kaffeeumeins commented Mar 24, 2019

The RFC7159 (https://www.ietf.org/rfc/rfc7159.txt)
and http://json.org/ descripted to encode the slahs with '/' but the current implementation does not encode the slash.

Do I miss something in the specification?

leadpony commented Mar 24, 2019

Hello @kaffeeumeins .
The RFC 7159 does not state the solidus U+002F MUST or SHOULD be encoded.

the characters that must be escaped:
quotation mark, reverse solidus, and the control characters (U+0000 through U+001F).

Please note that the unescaped chars in Chapter 7 contains %x23-5B, which includes the solidus.

lukasj transferred this issue from jakartaee/jsonp-api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment