Cannot load http://json-schema.org/draft-07/schema

[smoya]

Describe the bug

Current version of the Studio can't load http://json-schema.org/draft-07/schema when deployed in production.
This causes a warning on the editor such as:

How to Reproduce

Go to https://studio.asyncapi.com and load any AsyncAPI File.

Expected behavior

Warning should not be there.

The error is due to the fact the app is trying to load a http resource when the whole HTML has been loaded through https. This is illegal. In fact, the developer console is pretty clear:

​ Mixed Content: The page at 'https://studio.asyncapi.com/js/monaco/yaml.worker.bundle.js' was loaded over HTTPS, but requested an insecure resource 'http://json-schema.org/draft-07/schema'. This request has been blocked; the content must be served over HTTPS.

It seems we can provide a valid schema via monaco-yaml settings: https://github.com/remcohaszing/monaco-yaml/blob/main/index.d.ts#L4-L25

[magicmatatjahu]

The problem is in https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/2.2.0.json#L3 line, monaco-yaml try to resolve all external schemas from given version of AsyncAPI spec, so I think that we should create PR for specs, not for Studio.

[smoya]

The problem is in https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/2.2.0.json#L3 line, monaco-yaml try to resolve all external schemas from given version of AsyncAPI spec, so I think that we should create PR for specs, not for Studio.

What about using always https on all our schemas $schema field urls?

[magicmatatjahu]

What about using always https on all our schemas $schema field urls?

I had in mind that when I wrote my comment 😄

[smoya]

A PR has been created with the fix asyncapi/spec-json-schemas#115. Once merged, I guess we will need to redeploy the Studio so It loads all fresh schemas.