内容传输编码：BASE64 BOX-API [英] Content-transfer-encoding: BASE64 BOX-API

问题描述

我想知道BOX是否支持在多部分HTTP POST请求主体中使用的 Content-transfer-encoding：BASE64。

I would like to know if "Content-transfer-encoding: BASE64" used inside multipart HTTP POST request body is supported by BOX.

我遇到的问题是我生成了以下正文：

The problem I have is that I generated the following body:

-------boundary
Content-Disposition: form-data; name="filename"; filename="82b.gif"
Content-Type: image/gif
Content-Transfer-Encoding: BASE64

$base64_encoded_binary_file_content
-------boundary
Content-Disposition: form-data; name="parent_id"

123456789
-------boundary--

并将http请求发送到 https://upload.box。 com / api / 2.0 / files / content 。

and sent the http request to https://upload.box.com/api/2.0/files/content.

可以在此处创建文件，但与原始gif文件不同。它实际上是一个文本文件，其内容是由base64编码的原始gif文件的字符串。

The file can be created there, but it is not same as the original gif file. it is actually a text file whose content is a string of base64-encoded original gif file.

任何建议都会很有帮助。

any suggestion will be very helpful.

谢谢。

推荐答案

我们希望将来增加对文件的Base64编码的支持，但目前不支持。

We're looking to add support for Base64 encoding of files in the future, but do not currently support it.

这篇关于内容传输编码：BASE64 BOX-API的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！