Relevant changes coming to better serve meta-schemas #525
benjagm
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're making a slight change to the way we serve meta-schemas. In the past our website hosting situation has limited us from serving meta-schemas with the proper headers. With the release of the new website, we now have the opportunity to improve that situation.
What is changing?
Meta-schemas will now be served with Content-Type: application/schema+json
Meta-schemas will be served with Cache-Control headers that instruct HTTP caches to cache them
Meta-schemas will be accessible using CORS
What do you need to do?
We don't expect this change to effect anything you're currently doing with meta-schemas. It only enables more things you could do with them. If you make HTTP requests to fetch the official meta-schemas in your implementation or application, please make use of the new cache headers to properly cache those requests.
When is this change coming into effect?
This change is coming into effect next December 10th.
Related issue : website#199
Have questions? Let's continue the discussion. You can leave a comment here or connect with us on Slack.
Beta Was this translation helpful? Give feedback.
All reactions