Commit e73a650

committed

Core: add shared cache suggestion

1 parent ef6d322 commit e73a650Copy full SHA for e73a650

File tree

-1

lines changed

-1

lines changed

Lines changed: 3 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -526,7 +526,9 @@ Link: </alice>; rel="profile", </bob>; rel="profile"`
`526`	`526`	`When used for hypermedia systems over a network, <xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for distributing schemas. Misbehaved clients can pose problems for server maintainers if they pull a schema over the network more frequently than necessary, when it's instead possible to cache a schema for a long period of time.`
`527`	`527`	`</t>`
`528`	`528`	`<t>`
`529`		`- HTTP servers SHOULD set long-lived caching headers on JSON Schemas. HTTP clients SHOULD observe caching headers and not re-request documents within their freshness period.`
	`529`	`+ HTTP servers SHOULD set long-lived caching headers on JSON Schemas.`
	`530`	`+ HTTP clients SHOULD observe caching headers and not re-request documents within their freshness period.`
	`531`	`+ Distributed systems SHOULD make use of a shared cache and/or caching proxy.`
`530`	`532`	`</t>`
`531`	`533`	`<t>`
`532`	`534`	`Clients SHOULD set or prepend a User-Agent header specific to the JSON Schema implementation or software product. Since symbols are listed in decreasing order of significance, the JSON Schema library name/version goes first, then the more generic HTTP library name (if any). For example:`

Comments

(0)