Confusing value error message: The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

[ssbarnea]

I would like suggest replacement of the current confusing generic error message that we often get with something that better follows HTTP specification.

 The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

• Visiting https://json.schemastore.org sends user or https://json.schemastore.org/json/ which gives errors above. Clearly the domain root should not redirect to a 404 page, anything else would be better.
• Visiting https://json.schemastore.org/something-that-never-existed also gives the same error text
• https://json.schemastore.org/docker-compose also sends to the same page, and we do know that a docker-compose schema exists in the wild, instead of giving a confusing 404 message, it should redirect to either new location, or at least a ticket/web page that would the unlucky visitor some hints about what he should do.

Please put a correct HTTP 404 message, not one that gives 3 reasons all of them having specific HTTP codes different than 404.

Basically the message is a blatant lie where http code contradicts the text displayed to the user. I am sure "lie" was not intended but more of mistake when adding a custom http error page.

PS. Please keep the numeric code before the text.

[jasikpark]

Perhaps a proper 404 page with steps for how to contribute / report an issue would be helpful?

[jsoref]

root page

• https://json.schemastore.org should redirect to https://www.schemastore.org/json/ -- not https://json.schemastore.org/json/

deleted content

It'd be nice if there was an easy way to make landing pages for deleted content.

docker-compose is an example (but I've found others). Ideally such pages would be able to say:

docker-compose

410 (Schema rescinded)

Unfortunately, docker-compose is ambiguous and could refer to any of the following:

• x
• y
• z

See #x for more information / if you want to help

nonexistent-content

something-that-never-existed

404, SchemaStore does not appear to have a schema for something-that-never-existed.
It's possible you've misspelled it, in which case you can browse/search through the available schemas.
If you think it should, please consider filing an issue using link to template that includes fields for information about the schema.