Describe the bug
In REDCap's use of aws-sdk-php I found the client's header 'x-amz-user-agent' not being blacklisted in ./src/Signature/SignatureV4.php's function getHeaderBlacklist() and therefore authorization not working due to case sensitivity not matching 'X-Amz-User-Agent'. All of the other items in the blacklist are lower, shouldn't 'X-Amz-User-Agent' ? Or include in the blacklist both 'X-Amz-User-Agent' and 'x-amz-user-agent' ?
Regression Issue
Expected Behavior
All lower 'x-amz-user-agent' should be blacklisted
Current Behavior
'x-amz-user-agent' is not blacklisted
Reproduction Steps
Attempt to use REDcap's S3 implemention with an S3 endpoint and debug the reason the signature isn't working
Possible Solution
Add both 'x-amz-user-agent' and 'X-Amz-User-Agent' if needed
Additional Information/Context
No response
SDK version used
3.374.0
Environment details (Version of PHP (php -v)? OS name and version, etc.)
PHP 8.3.29
Describe the bug
In REDCap's use of aws-sdk-php I found the client's header 'x-amz-user-agent' not being blacklisted in ./src/Signature/SignatureV4.php's function getHeaderBlacklist() and therefore authorization not working due to case sensitivity not matching 'X-Amz-User-Agent'. All of the other items in the blacklist are lower, shouldn't 'X-Amz-User-Agent' ? Or include in the blacklist both 'X-Amz-User-Agent' and 'x-amz-user-agent' ?
Regression Issue
Expected Behavior
All lower 'x-amz-user-agent' should be blacklisted
Current Behavior
'x-amz-user-agent' is not blacklisted
Reproduction Steps
Attempt to use REDcap's S3 implemention with an S3 endpoint and debug the reason the signature isn't working
Possible Solution
Add both 'x-amz-user-agent' and 'X-Amz-User-Agent' if needed
Additional Information/Context
No response
SDK version used
3.374.0
Environment details (Version of PHP (
php -v)? OS name and version, etc.)PHP 8.3.29