replaced source :ruby gems by 'https://rubygems.org'
adding ./lib to $:
Updated unit tests for ruby 2.0

This diff adds support for using ruby 2.0 in the test suite by
disabling the S3CommandsTest since the aws/s3 gem in rubygems doesn't
support ruby 2.0 yet.  I also updated the Gemfile.lock to have newer
versions.  RightAWS now contains more tests to tickle execution paths
that were hit in S3CommandsTest.
Fix LS_BUCKET

GET foo.s3.amazonaws.com/ and GET s3.amazonaws.com/foo should result in
an LS_BUCKET request, but under the previous logic it would result in a
LIST_BUCKETS request. GET s3.amazonaws.com/ still results in a
LIST_BUCKETS request due to the 'if path == "/" and s_req.is_path_style'
conditional.

Signed-off-by: Shea Levy <shea@shealevy.com>
The Java client is sensitive to the case of the ETag header name.

Sadly, the WEBrick Response class's [] method downcase's header names
before putting them in the response header dictionary.  So 'ETag' ends
up 'etag'
which the AWS Java SDK doesn't recognize.  This simple fix replaces
response['ETag'] = ...  call with response.header['ETag'] = ...
test/botocmd.py - (idempotently) create bucket instead of relying on its existence
Version Bump
Version Bump Gemfile.lock
basic post support
remove extraneous puts and strip whitespace from start of xml response
update to current master and fix argument order in assert_match
reply to post with reasonable host
add bucket in post reply
Date formatting compatibility fixes

The Java AWS SDK expects the Last-Modified header to be in RFC 2616
format. It also expects the rest of the dates to use UTC for the
timezone.
Return CopyObjectResult

The Java AWS SDK expects this result on a successful copy.
FIX response body when S3 object is not found.

The previous implementation returned empty response body if s3 object has not been found.
This caused the problems in AmazonS3Client (at least the java implementation) which was not able
to parse the response body because it expected the xml error structure.

This fix returns the response body XmlAdapter.error_no_such_key in that scenario.
test_store_not_found added to check the case when the client tries to load nonexistent object from bucket.

In this case "NoSuchKey" exception should be thrown to reflect the error response returned from S3.
Merge pull request #19 from twalpole/post

basic post support
Code cleanup in post_test.rb
Don t clobber contents when copying in place

* also support replacing metadata for copy requests