added slick53 methods to boto route53
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Add proper to_print for LBR RRs in Route53
Merge remote-tracking branch 'upstream/develop' into develop
Remove disused imports.  Clean up namespace collision.  Part of #478
New __repr__ for ResourceRecordSets and Record.  #478

Incorporate more verbose __repr__ functions from Slick53, but
use to_print on Record to properly represent the more complicated
records (e.g. ALIAS, WRR, LBR)
Addition of an object-oriented Layer2 to Amazon's boto.swf
Allow for overloading class variable credentials through inheritance.
Add header support to multipart Upload Part - Copy

- Trivial change to all headers to be passed in to the
  copy_part_from_key() method and passed through to copy_key()
- Header support is required to set headers such as:
  * x-amz-copy-source-if-match
  * x-amz-copy-source-if-none-match
  * x-amz-copy-source-if-unmodified-since
  * x-amz-copy-source-if-modified-since
Fix for #1019 / rework of request building logic.
Merge branch 'master' of git://github.com/boto/boto
Integration and enhancement of slick53 #478 #272

Starting with a base from slick53: add support for LBR and
WRR records; add documentation; e-factor to pass record
objects opaquely and reduce code duplication; rename tests
file to test_layer2.py and add testing of LBR and WRR
records.
Update boto/cloudformation/connection.py

Extended the list of valid states.
Fix HmacAuthV4Handler to treat POST parameters properly.

I ran into this problem when digging into why AWS was returning HTTP 505 Version Not Supported
responses for autoscaling's CreateLaunchConfiguration action.  In past cases it looks like this
error has occurred when the query string of GET requests exceed some threshold (AWS likely reads a
fixed size and takes the last 5 bytes on the first line as the HTTP version).  Although the
AWSQueryConnection.get_object call was set to use POST the actual request consisted of a POST with
all of the parameters in the query string.

In researching this I figured out the logic to actually map request parameters into the query string
(GET requests) or into the request body (POST requests) actually occurs in the add_auth call in
_mexe shortly before the request is issued to Amazon.  For HmacAuthV4Handler there was no special
POST request handling so parameters always came in as query strings with the method 'POST'.

This patch does the following:

    (1) Moves the query string / request body manipulation on HmacAuthV4Handler to before the
canonical_request is calculated so that the request body signature is correctly generated.

    (2) Updates the canonical_uri to look at req.auth_path instead of req.path.  Since the query
string manipulation is occuring before the request is signed now we need to use the cached version
of this field that is set aside for authentication already.

    (3) Modify canonical_query_string to return '' when a POST request is used.  This is because the
parameters in a POST request will now be part of the body when calculating the canonical_request to
sign.

This appears to do the right thing in the cases I've tested.  It does blow away the contents of
request.body when their is a query string present so if anything ever attempts to make a POST call
with both params and data set bad things could happen.  This is just copying the behaviour already
present in QuerySignatureHelper when a POST request is processed.
Support multiple DBSecurityGroups for DBInstance.  Fixes #1086.
Fix HTTP timeouts for SSL connections

CertValidatingHTTPSConnection did not implement the http.HTTPConnection timeout argument correctly.  Newer Botos appear to use this connection instead of httplib.HTTPSConnection which breaks the [Boto]/http_connection_timeout configuration setting.

This patch sets the timeout on the new SSL socket if it has been configured.
Make proxy_ssl used configured timeout

The proxy_ssl method does not use the Boto [Boto]/http_connection_timeout setting when creating its socket.  This patch will configure the requested timeout if it is set in the http_connection_kwargs parameter.
Fix multipart uploads too big for default part size

The default part size of 4 MB is too small for any files over 40,000 MB, and there's no checking to ensure that a part size passed in is big enough.

I added a check to make sure the default part size is big enough. If it's not, the minimum part size needed is found and then it figures what what the smallest part size allowed by Amazon's API is and uses that instead.