changes to boto handling of HTTPS tunneled through a proxy

[Michael Schwartz]

Hi,

I committed a change on the boto develop branch today, to address a problem with using boto when tunneling HTTPS through a proxy. In the past, users would encounter an error like "EOF occurred in violation of protocol" when attempting to tunnel HTTPS through a proxy. The current change should solve that problem.

I don't believe any tunneling proxies depend on the older behavior (which sent an additional \r\n after the proxy auth headers), but if this change causes you problems you can revert to the older behavior by setting the following config variable in the [Boto] section of the .boto config file:

send_crlf_after_proxy_auth_headers = True

I would be interested in hearing from you if you find you need to set this config variable, including the make and version of the proxy server you are using.

For details on the decision to make this change please see this discussion.

Thanks,

Mike