mirror of
				https://github.com/zulip/zulip.git
				synced 2025-10-30 19:43:47 +00:00 
			
		
		
		
	api_docs: Add page documenting HTTP headers in the api docs.
Adds a page to the general api documentation about HTTP headers, so that information about the special response headers for rate limits have a more logical location in the docs and so that other HTTP header information can be shared, such as `User-Agent` conventions. Adjusts some text and linking on the rest-error-handling page and overview page for the REST API for the addition of the HTTP headers page.
This commit is contained in:
		
				
					committed by
					
						 Tim Abbott
						Tim Abbott
					
				
			
			
				
	
			
			
			
						parent
						
							d9d17eb87e
						
					
				
				
					commit
					dfb9f74017
				
			| @@ -14,37 +14,11 @@ for specific error conditions, since the `msg` strings are | ||||
| internationalized (e.g. the server will send the error message | ||||
| translated into French if the user has a French locale). | ||||
|  | ||||
| Each endpoint documents its own unique errors; below, we document | ||||
| Each endpoint documents its own unique errors; documented below are | ||||
| errors common to many endpoints: | ||||
|  | ||||
| {generate_code_example|/rest-error-handling:post|fixture} | ||||
|  | ||||
| To help clients avoid exceeding rate limits, Zulip sets the following | ||||
| HTTP headers in all API responses: | ||||
|  | ||||
| * `X-RateLimit-Remaining`: The number of additional requests of this | ||||
|   type that the client can send before exceeding its limit. | ||||
| * `X-RateLimit-Limit`: The limit that would be applicable to a client | ||||
|   that had not made any recent requests of this type. This is useful | ||||
|   for designing a client's burst behavior so as to avoid ever reaching | ||||
|   a rate limit. | ||||
| * `X-RateLimit-Reset`: The time at which the client will no longer | ||||
|   have any rate limits applied to it (and thus could do a burst of | ||||
|   `X-RateLimit-Limit` requests). | ||||
|  | ||||
| [Zulip's rate limiting rules are configurable][rate-limiting-rules], | ||||
| and can vary by server and over time. The default configuration | ||||
| currently limits: | ||||
|  | ||||
| * Every user is limited to 200 total API requests per minute. | ||||
| * Separate, much lower limits for authentication/login attempts. | ||||
|  | ||||
| When the Zulip server has configured multiple rate limits that apply | ||||
| to a given request, the values returned will be for the strictest | ||||
| limit. | ||||
|  | ||||
| [rate-limiting-rules]: https://zulip.readthedocs.io/en/latest/production/security-model.html#rate-limiting | ||||
|  | ||||
| ## Ignored Parameters | ||||
|  | ||||
| In JSON success responses, all Zulip REST API endpoints may return | ||||
|   | ||||
		Reference in New Issue
	
	Block a user