json-schema.org/schema 404

[6nv]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.83.0
• OS Version: MacOS Ventura 13.6

I've been getting a 404 not found error code from https://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.

Steps to Reproduce:

1. Create <file>.json (for example, schema.json)
2. Insert this code:

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

3. Notice this error, and intellisense is not working:
   

[gregsdennis]

This error is due to a revamped https://json-schema.org where we are only hosting HTTPS content. I believe we are serving a 301 from the meta-schema URLs, though.

Potential problems:

1. http://json-schema.org/schema should never be used to identify a meta-schema. This is not a valid meta-schema URI. Historically this URL hosted the latest meta-schema, but that led to unpredictable behaviors as new versions were released and the "latest" was updated, so we decided to remove it.
2. The value of $schema is to be interpreted as a URI, not a URL. If the value happens to also be a URL, it is not to be interpreted to actually be at that location. It is an identifier only.
3. Implementations (including editors) should not be downloading well-known meta-schemas. They should be packaged with the implementation. (@6nv, does the problem still occur if you use http://json-schema.org/draft-07/schema# or another well-known meta-schema URI?)

[6nv]

Some updates after meeting with the json-schema team:

• A Cloudflare redirection was added (@benjagm)
• http://json-schema.org/schema is deprecated and should not be used (@jdesrosiers)
• $schema is to be interpreted as a URI, not URL (@gregsdennis)

Here are some updates after the redirection was added, and restarting VS Code:

• New error message Problems loading reference
• Now, there are a few intellisense options (see image)

[6nv]

Last thing to add here for now: By default, draft-04 and draft-07 begin with http instead of https, however using either http or https works just fine for these schemas.

[benjagm]

however using either http or https works just fine for these schemas.

Yes, those redirections serves both http and https.

[aeschli]

I verified that we do not use or propose http://json-schema.org/schema in vscode or the json language service.
I created a PR to access json-schema.org always with https.

[gregsdennis]

@aeschli please be aware that the /schema route will likely not be available much longer. We have decided to discontinue it as it does not nap to a known meta-schema.

Furthermore, could you verify that the published meta-schema URIs are not downloaded, please? They should be considered well-known and supported offline. These definitely SHOULD NOT be regularly accessed by download.

• draft 4
• draft 6
• draft 7
• draft 2019-09
• draft 2020-12

We're not sure yet what the next iteration will be.

[gregsdennis]

@aeschli please confirm the other meta-schemas are not regularly downloaded. Otherwise this issue is NOT completed.

[aeschli]

We currently have a copy of draft-4 and draft-7 so there is no download for these. Others are downloaded, but they are cached locally.
I think this should be covered in a new issue. Please file against https://github.com/microsoft/vscode-json-languageservice.