feat: support range params in the policy #31
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.
Add support for content-length-range in CreateBrowserBasedSignature
Background
The current implementation of
CreateBrowserBasedSignature
doesn't support specifying upload size limits in the policy. Thecontent-length-range
condition is a critical feature for controlling the size of uploaded objects, but it cannot be added directly as amap[string]string
using the existing method.Proposal
This pull request implements support for the
content-length-range
condition as described in the OBS API documentation:https://support.huaweicloud.com/api-obs/obs_04_0012.html
Changes
ConditionRange
struct to represent range conditions:Usage
Users can now specify upload size limits when calling
CreateBrowserBasedSignature
: