however lets try to access the raw resource directly.
It is different from the currently downloaded spec, so I try to replace the link only first.
@zeitlinger@vadeg can you approve.
sorry still fails. :(
Looks like we correctly load the local schema as a JsonNode and then pass that to our JsonSchemaValidator with redirects setup for just http://json-schema.org/draft-04. I think, when validating the local schema internal references are being found and translated into absolute references, but nothing in the underlying validation understands that this is the the local schema that the process is starting from, and loads over http instead. Consequently adding an extra redirect for the originally loaded schema seems to hack around the problem - although I still suspect it means we're unnecessarily loading the original schema multiple times.
Yes, unless a cache in the parser is active to prevent this.