From 40152f4242dfe46a4c63ae69b0a0e1c83172f556 Mon Sep 17 00:00:00 2001 From: Tim Burke Date: Tue, 15 Nov 2016 14:12:02 -0800 Subject: [PATCH] Fix up X-Trans-Id-Extra docs Previously, they would render as "X -Trans-Id-Extra" Change-Id: Ibaf9b365467a2c91a0f03baed4d7bc36b0fa9967 --- api-ref/source/parameters.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index 23ab88a1a1..97ee990368 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -816,12 +816,12 @@ X-Trans-Id-Extra: Extra transaction information. Use the ``X-Trans-Id-Extra`` request header to include extra information to help you debug any errors that might occur with large object upload and - other Object Storage transactions. Object Storage appends the + other Object Storage transactions. The server appends the first 32 characters of the ``X-Trans-Id-Extra`` request header value to the transaction ID value in the generated ``X-Trans-Id`` response header. You must UTF-8-encode and then URL-encode the - extra transaction information before you include it in the ``X - -Trans-Id-Extra`` request header. For example, you can include + extra transaction information before you include it in the + ``X-Trans-Id-Extra`` request header. For example, you can include extra transaction information when you upload `large objects `_ such as images. When