Hsu Han Wen

Thank you for the updated information. However, the suggested solution did not work for me. I have checked the version of robotframework I am using and it does not seem...

#### Investigation: why aws-sdk-ruby test still fails In the AWS documentation — for example, [IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html), [S3 query parameter](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html) and [S3 Signature Calculations for the Authorization Header](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html) — it is stated...

During the implementation process, I noticed that Ozone doesn’t seem to validate mismatched values between signed headers and signed query parameters. According to the [AWS spec](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html): > If you add...

> Could you give some examples here? Currently I think we only check that all the headers in `X-Amz-SignedHeaders` should exist in the request headers. Regarding the actual HTTP header...

Hi @ivandika3, I tried a new implementation that introduces a runnable `preCommit` interface to perform validation before `commitKey`. This approach avoids adding S3-specific logic into `client.io`, so the validation can...

Thanks @ivandika3 for the feedback. I’ll switch to using a list of `preCommit` handlers instead and address the remaining follow-up items over the weekend, as I’m a bit busy recently....

@ivandika3 Got it — I’ll give this approach a try and evaluate the impact. This was actually my initial thought when exploring possible solutions. However, after some consideration, I hesitated...

Hi @ivandika3, I’ve updated this PR based on your feedback. Separately, I also experimented with making `O3SException` extend `IOException`, so it can be thrown directly from `preCommit`. Initially, this change...