You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: I am not entirely sure if the source of this issue lies within the scope of this library of any of its dependencies.
Situation
My (openAPI specification) JSON file contains a string with an unescaped DELETE control character, U+007F.
"examples" : {
"image/png" : "�" # should be U+007F (Github seems to redact this character)
},
Output of python -m openapi_spec_validator --schema 2.0 openapi-spec.json is:
unacceptable character #x007f: special characters are not allowed
in "<urllib response>", position 1082
If we replace the character by its encoded equivalent, like this:
"examples" : {
"image/png" : "\u007f"
},
the result is: OK
Expected
In my understanding, RFC 7159 (obsolete) RFC 8259 allows this specific control character to appear escaped and unescaped inside JSON strings: https://tools.ietf.org/html/rfc8259#section-7.
Therefore, I expect OK for both Inputs mentioned above.
The text was updated successfully, but these errors were encountered:
Note: I am not entirely sure if the source of this issue lies within the scope of this library of any of its dependencies.
Situation
My (openAPI specification) JSON file contains a string with an unescaped DELETE control character, U+007F.
Output of
python -m openapi_spec_validator --schema 2.0 openapi-spec.json
is:If we replace the character by its encoded equivalent, like this:
the result is:
OK
Expected
In my understanding,
RFC 7159 (obsolete)RFC 8259 allows this specific control character to appear escaped and unescaped inside JSON strings: https://tools.ietf.org/html/rfc8259#section-7.Therefore, I expect
OK
for both Inputs mentioned above.The text was updated successfully, but these errors were encountered: