http://json-schema.org/schema 404

[6nv]

Hi all,

I've been getting a 404 not found error code from http://json-schema.org/schema in VS Code and in multiple different browsers, and on different networks. Additionally, VS code no longer provides intellisense when I use that schema URL.

Sample code to reproduce:

{
    "$schema": "http://json-schema.org/schema"
}

[gregsdennis]

Hey @6nv.

There are a couple problems here.

First, we are only serving HTTPS from the website now.

Second, meta-schemas should be packaged with the editor/implementation rather than downloaded as needed. That's an issue with the editor. We expected this.

There have been other reports of implementations doing this, and our response is the same. You're welcome to follow the conversation in Slack as well.

I'll open an issue with VSCode.

[gregsdennis]

@6nv you might try http://json-schema.org/draft-07/schema#. This would be a better option than that URI.

[benjagm]

Hi everyone! I just deployed a new rule on cloudflare to create that redirect for https://json-schema.org/schema.
This was a missing redirection rule in the migration process. @6nv Could you please try again and let us know?

[jdesrosiers]

Keep in mind that the use of http://json-schema.org/schema# is deprecated and should not be used. Consider this outage a dress rehearsal for when we stop serving it altogether 😉.

In Draft 4, a $schema value of http://json-schema.org/schema# referred to the latest version of JSON Schema. This usage has since been deprecated and the use of specific version URIs is required. - https://json-schema.org/understanding-json-schema/basics#declaring-a-json-schema

we are only serving HTTPS from the website now.

I just want to clarify that the website does respond to http: requests, it will just give a 301 redirect to the https: address. As long as the client (vscode in this case) handles HTTP redirects the way it should, you shouldn't notice any difference.

[6nv]

FYI, issue created with VS Code here: microsoft/vscode#195189

[gregsdennis]

That VSCode issue has been closed via PR.

@6nv are you happy closing this?

[6nv]

It would be nice-to-have to access the latest schema using /schema but it appears that it's not recommended to do that. If that's still the case, I think this issue can be closed.

[benjagm]

As per the Open Community Working Meeting of 2023-10-30 this is going to be deprecated in the future.
json-schema-org/community#505

[benjagm]

Closed as completed.