Can't access file resource from network context about json-schema-core

[jdesrosiers]

The error is in response to this.

JSC can fetch schemas from the web or from the file system, but when fetching from the file system, there are limitations for security reasons. If your schema has an identifier with an http scheme (http://example.com/my-schema), it's not allowed to reference schemas with a file scheme (file:///path/to/my/schemas/my-schema.json).

I'm looking into it and there seems to bug where this error is firing when it shouldn't. I should have a fix out this afternoon. I'll also look into improving that error message. It's not very helpful without knowing which file was requested and what the context URL is.

Does your schema have an $id or $ref with an http scheme? Without knowing what your schema looks like (and the limited error messaging), I can't say if you are getting this error for good reason, or because of the bug.

[jdesrosiers]

Here's an example of something that should cause that error. Because the $id is http (network context), it isn't allowed to $ref a file.

{
  "$id": "http://example.com/example.schema.json",
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "type": "object",
  "properties": {
    "foo": { "$ref": "file:///path/to/my/schemas/example.schema.json" }
  },
  "required": ["foo"]
}

[aecollver]

Here's an example schema where I see this error (it doesn't have an $id):

{
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "type": "object",
  "properties": {
    "name": {
      "title": "Target Name",
      "description": "Target names must begin and end with letters, but may contain numbers, hyphen and underscore.",
      "type": "string",
      "pattern": "^[A-Za-z]([\\w\\-]*[A-Za-z])?$"
    }
  },
  "required": [
    "name"
  ]
}

I did unsuccessfully try other variations like the $id like in your example and "$id": "file:///path/to/my/schema.json"

[jdesrosiers]

There are no $refs in that schema, so there shouldn't be any problem. Your schema is fine. You're just hitting the bug.

[jdesrosiers]

I just published the fix. Please try it out and let me know if it's working for you.

NOTE: The bug was in json-schema-core, not in json-schema-validator where the bug was reported, so when you update you should expect to see a version bump in the json-schema-core dependency.

[aecollver]

Thank you for fixing this!