[s3-dev] AWS::S3::SignatureDoesNotMatch error when content-type can't be inferred

[Marcel Molina Jr.]

On Fri, Dec 15, 2006 at 11:15:48AM -0500, Stephen Caudill wrote:
> >Hey Stephen, thanks for reporting this.
> >
> >Someone brought this up a few weeks ago (http:// 
> >developer.amazonwebservices.com/connect/message.jspa? 
> >messageID=49153#49156) and at the time I couldn't recreate
> >it. I still can't recreate it actually, which is weird:
> >
> >>>S3Object.store('s3sh', File.open('/opt/local/bin/s3sh'), 'marcel')
> >  => #<AWS::S3::S3Object::Response:0x10993930 200 OK>
> 
> Hmm... that is weird. I wonder if it's an environment thing?
> 
> I'm on a MacBook Pro.  Here's my Ruby version, straight from the  
> horses mouth:
> 
> [10:38:37][caudill at lazuli][caudill]$ ruby -v
> ruby 1.8.5 (2006-08-25) [i686-darwin8.8.1]
> 
> I noted that you have a test that specifically checks to ensure that  
> you can store a file with no extension and no content-type  
> specified... which passes on my computer, only further adding to my  
> befuddlement.
> 
> Hmmm... I think I've got a box that's running ruby 1.8.4, let me give  
> that a whirl.

Ok. I've got ruby 1.8.0, 1.8.2, 1.8.4 and 1.8.5 installed and can now run the
tests against all these versions. I'll be able to debug differences between
different versions of ruby now.

marcel
-- 
Marcel Molina Jr. <marcel at vernix.org>