fix api overview document
The content about Object Storage HTTP requests constraints seems to be a table but broken, this patch fixes it into correct rst table format. Change-Id: I1b4c62da3e6d91add3ee0218707c1628c8f04b33
This commit is contained in:
parent
170313d7db
commit
a88bd6e6b9
@ -133,21 +133,16 @@ or ends.
|
||||
Object Storage HTTP requests have the following default constraints.
|
||||
Your service provider might use different default values.
|
||||
|
||||
==== ============= =====
|
||||
============================ ============= =====
|
||||
Item Maximum value Notes
|
||||
==== ============= =====
|
||||
|
||||
============================ ============= =====
|
||||
Number of HTTP headers 90
|
||||
|
||||
Length of HTTP headers 4096 bytes
|
||||
|
||||
Length per HTTP request line 8192 bytes
|
||||
|
||||
Length of HTTP request 5 GB
|
||||
|
||||
Length of container names 256 bytes Cannot contain the ``/`` character.
|
||||
|
||||
Length of object names 1024 bytes By default, there are no character restrictions.
|
||||
============================ ============= =====
|
||||
|
||||
You must UTF-8-encode and then URL-encode container and object names
|
||||
before you call the API binding. If you use an API binding that performs
|
||||
|
Loading…
Reference in New Issue
Block a user