TripleEmcoder/openwrap — comment on commit 13f59c1d9769d63b1f1219f3dcfee1fd57b01604
File:  line 0
By serialseb:

Are you signing the request on the way out? http://s3.amazonaws.com/doc/s3-developer-guide/RESTAuthentication.html seems to indicate that they use yet another completely random and non-restful system to sign headers, i'd assume they'd think that the request coming in has an unknown header that was not signed and this is failing?

We could special-case for amazon but I'd think that sucks a bit. We could just default to content-type application/octet-stream, that would probably work just fine, although I'm wary of obfuscating things like that. How do you craft a POST to the amazon endpoint, through the publish uri? If that's the case I'd think that you could get away with pre-signing the expected http headers with the querystring option?