From 39d8526e3b986f42cce3d476319051238d5424e7 Mon Sep 17 00:00:00 2001 From: David Lawrence Date: Tue, 26 Jan 2016 15:17:18 +0000 Subject: Bug 1240752 - Attachment data submitted via REST API must always be base64 encoded r=gerv,a=dkl --- docs/en/rst/api/core/v1/attachment.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/en/rst/api/core/v1/attachment.rst b/docs/en/rst/api/core/v1/attachment.rst index 22a57af60..6c80651c1 100644 --- a/docs/en/rst/api/core/v1/attachment.rst +++ b/docs/en/rst/api/core/v1/attachment.rst @@ -140,7 +140,7 @@ To create attachment on a current bug: "is_markdown" : true, "summary" : "Test Attachment", "content_type" : "text/plain", - "data" : "(Some patch content)", + "data" : "(Some base64 encoded content)", "file_name" : "test_attachment.patch", "obsoletes" : [], "is_private" : false, @@ -165,9 +165,7 @@ name type description **ids** array The IDs or aliases of bugs that you want to add this attachment to. The same attachment and comment will be added to all these bugs. -**data** string The content of the attachment. If the content of the - attachment is not ASCII text such as - ``application/octet-stream`` you must encode it in +**data** base64 The content of the attachment. You must encode it in base64 using an appropriate client library such as ``MIME::Base64`` for Perl. **file_name** string The "file name" that will be displayed in the UI for -- cgit v1.2.3-24-g4f1b