Retrofit2 urlencode 编码的问题

最新推荐文章于 2024-07-11 17:50:45 发布

迦蓝叶

最新推荐文章于 2024-07-11 17:50:45 发布

阅读量1w

点赞数 1

分类专栏： Android 文章标签： retrofit2 编码 urlencode

本文链接：https://blog.csdn.net/soslinken/article/details/51543437

版权

Android 专栏收录该内容

79 篇文章 0 订阅

订阅专栏

前言

很抱歉，造成了将近2000位同仁看了之前的这篇博客，造成了错误的理解，在此说声抱歉，重写一次博客，修正一下之前的有问题的理解。

Retorfit Urlencode

其实Retorfit并不管理urlencode。所以所有关于Retorfit 设置Urlencode的方式都是无效的。
Github 上关于 Urlencode 相关问题中 JakeWharton 的回复

So Retrofit doesn’t actually control this. It comes from OkHttp’s FormBody type which uses this list for encoding. However, your server should be percent-decoding these values to the same thing. The whole point of percent encoding is to avoid ambiguity. In theory you could percent encode every single character. That said, the current set comes from the behavior of major browsers (Chrome and Firefox) so someone posting from an HTML form would produce the same version.

关于encoded 的设置

还是 JakeWharton在GitHub上的一个回复作为解释

encoded=true means your value was already encoded with respect to the requirements of form URL bodies. As you found, we simply tell OkHttp that this was the case, and if it meets OkHttp’s requirements for what passes as properly encoded it will be included unmolested. Otherwise OkHttp tries to correct the lack of proper encoding. It does not mean that the raw value you pass will always be used.

说的很清楚，这个值仅仅是一个建议值，它用来给Okhttp建议说，这个已经编码过了，但是如果在Okhttp检查的时候，这个不符合Urlencode的规则，那么还是会给你编码，而不是设置了这个值就使用你传递的字符串进行交互。

可以在这里额外考虑一下，如果设置为True 自行使用UrlEncode工具格式化之后，是否可以修复自动UrlEncode时出现的字符集问题？没测试过，只是一个猜想。。。