This commit fixes a bug where vpc_id attribute is not set on a newly created group object when using vpc_id kwarg of create_security_group(). This breaks all of the authorize, revoke, and delete security group convenience methods for VPC-linked groups. A separate call to get_all_security_groups() to re-fetch the group correctly includes the vpc_id but this fix ensures that the object immediately returned after creating a VPC-linked group has the proper vpc_id attribute.
…default (overridable by new send_crlf_after_proxy_auth_headers config variable)
- support version_id in the key or as passed from generate_url params - Don't add non-provider headers to the generated url (see below) - Fixed missing url encoding before passing to sig generation so that it can correctly decode the params. This is similar to pull request #646 which can now also be closed. - Fixed the headers dictionary polution with response-headers that was happening as part of calling the generate_url function. - Added small unit test as provided by pull request #646 also. I also confirmed that everything still works for the PUT case described in the following url. Note though that, the url no longer contains the Content-Length nor is it required at all as it's not part of the signature calculation anyway. I confirmed also that adding other headers such as --header "Content-Type: text/plain" to curl work when you specify same header what you pass to generate_url via headers dict. http://stackoverflow.com/questions/10044151/how-to-generate-a-temporary-url-to-upload-file-to-amazon-s3-with-boto-library Both s3 and gs unit tests pass.
…ridden in the boto config file.