-
-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s3cmd v2.0.0 with Python 2.7.9 using SSL behind Squid Proxy, getting "ERROR: S3 error: 400 (Bad Request)" #905
Comments
After several tries and tests, I figured I would try an older version and downgraded to v1.6.1 - to my surprise, it works! Seems like there's regression from v1.6.1 -> v2.0.0 with regard to proxied SSL connections. here's a debug output using v1.6.1:
|
Some further testing revealed that although with Debug output:
|
Ping :-) Any ideas? |
I have a little back log of issues to process but don't worry i will have a
look.
Le 9 août 2017 6:30 PM, "Danny Kulchinsky" <[email protected]> a
écrit :
Ping :-)
Any ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#905 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABAUpKidUo6DiRTJf4bJiqw8iIZwIutiks5sWd6PgaJpZM4OmBMx>
.
|
@fviard thank you! |
Thank you for the detailed log. I have an idea, is it possible for you to try a small change to see if it solves your issue?
I think that in the default case when no custom port set, then we create the tunnel with connect without specify the destination port. Thinking that the proxy will guess alone. |
Thanks for this! Could you please post again the diff as above is not very clear. |
Okay, so I figured out what had to be changed (I think), this is the updated block:
And the good news! it works 👍 tested |
Here's my actual diff, just in case :)
|
Great! any plans to have a release anytime soon with this (and other) fixes? We use Puppet + pip to deploy s3cmd, so would prefer an official release (instead of pulling from Git). |
Yes, I hope to be able to do a new version in a few days. |
Great! looking forward to it :-)
…On 19 August 2017 at 10:56, Florent Viard ***@***.***> wrote:
Yes, I hope to be able to do a new version in a few days.
A lot of issues have been found and fixed since the last release and the
initial support of python 3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#905 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AXJk7JePY4OZkQkI6WoG5e5Ng6WuzYt-ks5sZveLgaJpZM4OmBMx>
.
|
Any update about the next release 😊 |
Hey guys,
I'm running s3cmd v2.0.0 on Debian Jessie (8.7) with Python 2.7.9.
We have a Squid proxy in place and when setting up s3cmd with SSL (
use_https = True
) s3cmd fails withERROR: S3 error: 400 (Bad Request)
error. Withuse_https = False
everything works perfectly.UPDATE: I performed two tests
UPDATE 2: test 3 - 5
aws-cli (v1.11.127)
on the same node and it works just fine (I verified it uses our proxy and HTTPS):I configured the server to not use a Proxy and it works too
Tried with Python 3 (3.4.2) -> doesn't work
Tried with Buckets in different regions (Ireland, Oregen) -> doesn't work
Upgraded Squid from 3.4.8 to 3.5.25 -> didn't help
Based on above, it seems like some kind of combination between s3cmd and Squid that just doesn't work. However, we have many other HTTPS connections going through this Proxy using the CONNECT method without any issues...
Here is a debug snippet:
This seems like an issue with our Proxy, however I can't seem to figure out what.
The text was updated successfully, but these errors were encountered: