Incorrect content type headers on hosted schemas #4858
Description
Area with issue?
Web server
✔️ Expected Behavior
Hosted schemas have a Content-Type: application/schema+json (or at least application/json) header.
❌ Actual Behavior
Hosted schemas have a Content-Type: application/octet-stream header.
Fetching json.schemastore.org schemas first redirects to www.schemastore.org (the 301 response has an HTML content type, which is fine, it's just a redirect), but then fetching the schema from www.schemastore.org returns an octet stream content type.
This causes problems for tools that validate the content type, e.g. we had tooling that switched from processing remote schema references as nested schemas to processing the remote references as straight inline text. This started happening some time in May/early-June 2025.
We started relying on local copies of the schemas as a workaround.
JSON, YAML, or TOML file that does not work.
No response
IDE or code editor.
None
Are you making a PR for this?
No, someone else must create the PR.