Bug #6152
closedNew S3 auth code fails when using response-* query string params to override response headers
0%
Description
Previously there was a list of subresources to ignore when generating a signature. This has changed to a list of subresource to sign but the response-* were not included as they should have been.
Attached is a tested fix.
Files
Updated by Ian Colle over 10 years ago
- Assignee set to Yehuda Sadeh
- Priority changed from Normal to High
- Target version deleted (
v0.67 - Dumpling)
Updated by Yehuda Sadeh over 10 years ago
- Status changed from New to Pending Backport
Updated by Yehuda Sadeh over 10 years ago
- Status changed from Pending Backport to Resolved
Was already merged into dumpling (commit:9b953aa4100eca5de2319b3c17c54bc2f6b03064).
Updated by Sylvain Munaut over 10 years ago
That commit has nothing to do with this issue ... this commit is from Februrary and related to duplicate content type headers ...
This issue is related to S3 signature computations ...
Updated by Benjamin Gilbert over 10 years ago
This is still broken on 0.67.4. Please consider backporting the fix (7a7361d7) to Dumpling.
Updated by Yehuda Sadeh over 10 years ago
I sent a pull request a few days ago, so this should be in the next dumpling release.
Updated by Yehuda Sadeh over 10 years ago
- Status changed from Resolved to Pending Backport
Updated by Yehuda Sadeh over 10 years ago
- Assignee changed from Yehuda Sadeh to Josh Durgin
This is still waiting for merge (sent a pull request a week ago).
Updated by Josh Durgin about 10 years ago
- Status changed from Pending Backport to Resolved
- Assignee changed from Josh Durgin to Yehuda Sadeh
backported in commit:4e47a003bb3adcee690067d4037c248a93023c20 a while ago