This pull request implements the new 'setting response headers on signed urls' added to S3 on january 14, 2011, which allows clients to generate signed URLs that change the response headers for a file stored in S3 without having to call S3 directly (something that's really nice if you use S3 as a virtual filesystem, as you could now rename files and not have to rename them - setting content-disposition - on the real s3 storage).
My last two commits fix an issue with rbroemeling/right_aws code where you could not add more than one parameter (the signing would fail), fixing some funky unecessary URL unescaping, fixing some of the S3 tests and also adding 3 new tests proving that the new code works.
The main issue was that S3 expects the parameters to be ordered (alphabetically) and his original code wasn't accounting for this. The 3 new tests also try with different parameters to make sure that it really works as expected.
This pull request implements the new 'setting response headers on signed urls' added to S3 on january 14, 2011, which allows clients to generate signed URLs that change the response headers for a file stored in S3 without having to call S3 directly (something that's really nice if you use S3 as a virtual filesystem, as you could now rename files and not have to rename them - setting content-disposition - on the real s3 storage).
My last two commits fix an issue with rbroemeling/right_aws code where you could not add more than one parameter (the signing would fail), fixing some funky unecessary URL unescaping, fixing some of the S3 tests and also adding 3 new tests proving that the new code works.
The main issue was that S3 expects the parameters to be ordered (alphabetically) and his original code wasn't accounting for this. The 3 new tests also try with different parameters to make sure that it really works as expected.