增加了两条APIv3的测试用例，示例说明图片下载及上传的特殊用法 #85
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM |
tpirc3
approved these changes
Mar 11, 2022
xy-peng
approved these changes
Mar 11, 2022
This was referenced May 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
消费者投诉图片下载及应诉反馈图上传两个场景，其中图片下载在资源标识含pct-encoded字符串时，uri-template并不能保证资源标识的准确性，详细见 pct-encoded reserved character(%2F) was encoded twice guzzle/uri-template#18 , 示例以testUseStandardGuzzleHttpClient下载，可保证请求签名的资源，与真正请求的资源是一致的;hash()方法的返回数据签名调整;