如何问Retrofit2，对我的动态URL不编码？

Question

我正试图将我的代码库从1.9版本升级到2.0版本。我在1.9版本中上传图像没有问题。然而，我得到以下S3响应错误后，我改变到2.0版本。

这是我在Retrofit v1.9中上传图像的界面：

public interface IFileUploadAPI
{
    @PUT("/{url}")
    void uploadFile(@Path(value = "url", encode = false) String url, @Body() TypedFile file,
                    Callback<UploadFileResponse> callback);
}

我已将其更改为改装v2.0时的以下代码：

public interface IFileUploadAPI
{
    @PUT
    Call<UploadFileResponse> uploadFile(@Url String url, @Body RequestBody file);
}

我就是这样实现的。

public class MyFileUploadAPI
{
    private IFileUploadAPI mService;

    public MyFileUploadAPI()
    {
        final Retrofit adapter = new Retrofit.Builder() //
                        .baseUrl(MyAPIConstant.API_URL_BASE) // This URL will be ignored as we are using dynamic url. So no matters what it is.
                        .addConverterFactory(GsonConverterFactory.create(GsonUtils.getGson())) //
                        .client(ASDKApplication.getInstance().getOkHttpClient()) //
                        .build();

        this.mService = adapter.create(IFileUploadAPI.class);
    }

    public void uploadFile(final String url, final String filePath, final String mimeType)
    {
        RequestBody file = RequestBody.create(MediaType.parse(mimeType), filePath);
        Call<UploadFileResponse> call = mService.uploadFile(url, file);
                call.enqueue(new Callback<HitchUploadFileResponse>()
        {
            @Override
            public void onResponse(Call<UploadFileResponse> call, Response<UploadFileResponse> response)
            {
                UploadFileResponse uploadFileResponse = new UploadFileResponse();

                if (response.isSuccessful() && response.body() != null)
                {
                    uploadFileResponse = response.body();
                }

                // Rest of code...
            }

            @Override
            public void onFailure(Call<UploadFileResponse> call, Throwable t)
            {
                Logger.error(TAG, "uploadFile.onFailure(), msg: " + t.getMessage());
            }
        }
    }
}

因此，当用户单击＜code＞上传＜/code＞按钮时，我调用一个API，它会返回一个我必须调用的url。回答如下：

[{"uploadSignedURL":"https://my-account.s3.amazonaws.com/license/1000_front_1464988248.jpeg?AWSAccessKeyId=MY_ID\u0026Expires=1464991848\u0026Signature=NhStdEX8RH3J0uzvVa6h%2FvN6FZQ%3D","filePath":"license/1000_front_1464988248.jpeg","target":"driving_license_front_img"}]

最后是对上述url的调用的响应（http状态代码403禁止）：

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>MY_ID</AWSAccessKeyId><StringToSign>PUT

image/jpeg; charset=utf-8
1464991848
/my-account/license/1000_front_1464988248.jpeg</StringToSign><SignatureProvided>NhStdEX8RH3J0uzvVa6h/vN6FZQ=</SignatureProvided><StringToSignBytes>50 55 54 0a 0a 69 6d 61 67 65 2f 6a 70 65 67 3b 20 63 68 61 72 73 65 74 3d 75 74 66 2d 38 0b 31 34 36 34 39 39 31 38 34 38 0a 2f 6d 79 74 65 6b 73 69 3a 67 72 61 62 68 69 45 63 68 2f 6c 69 63 65 6e 73 65 2f 31 30 30 30 5f 66 72 6f 6e 74 5f 31 34 36 34 39 38 38 32 34 38 2e 6a 70 65 67</StringToSignBytes><RequestId>2D6D08FE4E34FCE5</RequestId><HostId>tpvmJdeRxtAzPxOk2zFwMF2Ne6hmNMkcaM9D7m/I13iynYGJyqtC0U72B2t41SDYfPBjCRTVyOY=</HostId></Error>

Answer 1

好吧，我发现出了什么问题。

okhttp正在将charset=utf-8添加到我的内容类型中。因此，我的内容类型变得像这样 contentType：image/jpeg; charset=utf-8。我在Postman上进行了测试，通过删除; charset=utf-8，我可以上传我的图像。

https://stackoverflow.com/a/25560731/513413说明添加＜code＞字符集＜/code＞的原因。这是因为我正在传递图像文件的路径。你可以很容易地改变

RequestBody file=requestboid.create（MediaType.parse（mimeType），filePath）

自

RequestBody file = RequestBody.create（MediaType.parse（mimeType）， new File（filePath））;

还有一件更重要的事。一旦你上传你的图片到S3，亚马逊返回HTTP状态码200和空的正文。所以你也必须改变界面。

public interface IFileUploadAPI
{
    @PUT
    Call<Void> uploadFile(@Url String url, @Body RequestBody file);
}