Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
15.0.0, 15.0.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: May 31, 2019
The JSON schema validation feature released in 15.0.0 supports only the following reference-resolving functionality: -- Support of local references and definitions (in-file or in secondary schema file) during schema load. -- An external reference is fully matched against the base ID of a secondary file, up to the fragment identifier, after which it is internally resolved within the secondary file. The validator does not support the following: -- Network fetching of external schema files. -- Assumptions regarding filesystems, such as matching file name to ID. -- Internal or external base ID modification. Each schema must contain a root base ID, and fragments are only resolved internally; fragments containing IDs are not supported.
Schema files cannot be uploaded and used for JSON traffic validation.
-- Attempted upload of JSON schema files. -- JSON schema validation on uploaded schema. -- Schema contains unsupported references which validator is unable to resolve.
Schema can be modified in any of the following ways: -- Definition of all references in main schema file. -- Use of full path in all references and IDs. -- Use of supported types of references such as full path followed by fragment identifier and internal path.