Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
dev:web_api:v3:types_and_fields [2015/04/14 19:31]
fcheslack
dev:web_api:v3:types_and_fields [2019/06/17 19:36]
dstillman
Line 5: Line 5:
 As schema changes are currently rare, clients should cache type/field data for a period of time (e.g., one hour) without making further requests. Subsequent requests for new data should then include ''​If-Modified-Since''​ headers containing the contents of the ''​Last-Modified''​ header from the original response. If no changes have occurred, the server will return a ''​304 Not Modified''​ and clients should continue to use cached data for the same period of time. //​[Conditional requests are not yet implemented.]//​ As schema changes are currently rare, clients should cache type/field data for a period of time (e.g., one hour) without making further requests. Subsequent requests for new data should then include ''​If-Modified-Since''​ headers containing the contents of the ''​Last-Modified''​ header from the original response. If no changes have occurred, the server will return a ''​304 Not Modified''​ and clients should continue to use cached data for the same period of time. //​[Conditional requests are not yet implemented.]//​
  
-User-friendly type/field names will be returned in English by default. Clients can request names in other languages by passing a ''​locale''​ parameter (e.g., ''​GET /​itemTypes?​locale=fr-FR''​). ​//​[Non-English locales are not yet implemented.]//​+User-friendly type/field names will be returned in English by default. Clients can request names in other languages by passing a ''​locale''​ parameter (e.g., ''​GET /​itemTypes?​locale=fr-FR''​).
  
 ==== Getting All Item Types ==== ==== Getting All Item Types ====
dev/web_api/v3/types_and_fields.txt ยท Last modified: 2019/12/07 18:46 by tomas_fiers