Commit e5a69b5d authored by David Lawrence's avatar David Lawrence

Bug 1240752 - Attachment data submitted via REST API must always be base64 encoded

r=gerv,a=dkl
parent 5de72e1a
...@@ -139,7 +139,7 @@ To create attachment on a current bug: ...@@ -139,7 +139,7 @@ To create attachment on a current bug:
"comment" : "This is a new attachment comment", "comment" : "This is a new attachment comment",
"summary" : "Test Attachment", "summary" : "Test Attachment",
"content_type" : "text/plain", "content_type" : "text/plain",
"data" : "(Some patch content)", "data" : "(Some base64 encoded content)",
"file_name" : "test_attachment.patch", "file_name" : "test_attachment.patch",
"obsoletes" : [], "obsoletes" : [],
"is_private" : false, "is_private" : false,
...@@ -164,9 +164,7 @@ name type description ...@@ -164,9 +164,7 @@ name type description
**ids** array The IDs or aliases of bugs that you want to add this **ids** array The IDs or aliases of bugs that you want to add this
attachment to. The same attachment and comment will be attachment to. The same attachment and comment will be
added to all these bugs. added to all these bugs.
**data** string The content of the attachment. If the content of the **data** base64 The content of the attachment. You must encode it in
attachment is not ASCII text such as
``application/octet-stream`` you must encode it in
base64 using an appropriate client library such as base64 using an appropriate client library such as
``MIME::Base64`` for Perl. ``MIME::Base64`` for Perl.
**file_name** string The "file name" that will be displayed in the UI for **file_name** string The "file name" that will be displayed in the UI for
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment