![]() But if a request fails for some call-specific reason, v1 might have returned any of 403, 404, 406, 411, etc. For errors that are common to all API calls, we do the same thing as before: 400 for bad request, 401 for auth failure, 429 for rate limiting, etc. We've also simplified our use of HTTP status codes for errors. This allows browsers and HTTP client libraries to transparently cache that data for you. file contents) support HTTP GET and ETag-based caching. For example, endpoints that return bulk binary data (e.g. We will continue to use other HTTP features in specific cases where they provide concrete benefits. ![]() Requests take JSON in the body and responses return JSON in the body. For example, most endpoints always use HTTP POST, including those that return structured data. Overall, we've simplified our use of HTTP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |