ZF2-409: After upgrading from beta4 to beta5 the S3 service stopped working

Issue Type: Bug Created: 2012-07-19T12:08:07.000+0000 Last Updated: 2012-07-23T16:09:37.000+0000 Status: Resolved Fix version(s): Reporter: Boris (boristm) Assignee: Maks 3w (maks3w) Tags: - Zend\Cloud

  • amazon

Related issues: Attachments:


After upgrading from beta4 to beta5 the S3 service stopped working: all the operations (for example, getBuckets) leads to an error in the response of the service: 'The request signature we calculated does not match the signature you provided. Check your key and signing method.'

In beta4 it works.

I've checked the difference between beta4 and beta5 and found the calculating of signature was changed in addSignature method of S3 class.

In beta4 it was:

<pre class="highlight">
$signature = base64_encode(Hmac::compute($this->_getSecretKey(), 'sha1', utf8_encode($sig_str), Hmac::OUTPUT_BINARY));

In beta5 it is:

<pre class="highlight">
$signature = base64_encode(Hmac::compute($this->_getSecretKey(), 'sha1', utf8_encode($sig_str), true));

Could you please explain why the last argument of Hmac::compute was changed in this way? Or if it was made by mistake could you roll back this?


Posted by Maks 3w (maks3w) on 2012-07-19T12:22:23.000+0000

Created PT…

Posted by Maks 3w (maks3w) on 2012-07-23T16:09:37.000+0000

Patch merged.

Watchout that now the code for Amazon Services lives in

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.