fog/fog — pull request #2198 by soulcutter (2013-09-30 19:59:10+00:00)
Title: Fix AWS S3 POST object restore SignatureDoesNotMatch error

POST object restore was using the bucket_name as a host prefix rather than in the canonical path as AWS was expecting. This resulted in getting results such as:

```xml

SignatureDoesNotMatch

The request signature we calculated does not match the signature you provided.
Check your key and signing method.

…
…
…
…
POST
AAjA1/2lcgEFNlhuhHDHBw==
application/xml
Mon, 30 Sep 2013 18:08:03 +0000
{bucket_name}/{object_name}?restore
…

```

I narrowed it down to the StringToSign generated by `post_object_restore` not including the bucket_name. I'm not sure why this used to work honestly. Maybe AWS got stricter?