openstack
/
openstack-manuals
Code Issues Proposed changes

Make updates to change HTTP response code as needed. 

There were changes needed to conform compliance with
RFC2616. Updated code number and description accordingly.

Change-Id: Ie7fd6ad34095bb7857c69e6d1da2ea1453ecc60b
Partial-Bug: #1355548
Related-Bug: #1298131
This commit is contained in:
Steven Deaton 2014-09-01 00:42:02 -05:00
parent 14588078ae
commit 17793e38ce
2 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/common/section_compute_config-api.xml
View File

@ -38,11 +38,8 @@
to configure limits on the type and number of API calls
that can be made in a specific time interval.</para>
<para>When API rate limits are exceeded, HTTP requests return
an error with a status code of <errorcode>413</errorcode>
<errortext>Request entity too large</errortext>, and
includes an HTTP <literal>Retry-After</literal> header.
The response body includes the error details and the delay
before you should retry the request.</para>
an error with a status code of <errorcode>403</errorcode>
<errortext>Forbidden</errortext>.</para>
<para>Rate limiting is not available for the EC2 API.</para>
</simplesect>
<simplesect>

3
doc/config-reference/object-storage/section_object-storage-features.xml
View File

@ -469,8 +469,7 @@ Sample represents 1.00% of the object partition space
scope of containers that are delegated to non-admin users, exposed to formpost uploads,
or just as a self-imposed sanity check.</para>
<para>Any object PUT operations that exceed these quotas
return a 413 response (request entity too large) with a
descriptive body.</para>
return a 403 response (forbidden).</para>
<para>Quotas are subject to several limitations: eventual
consistency, the timeliness of the cached container_info
(60 second TTL by default), and it is unable to reject