[
https://issues.apache.org/jira/browse/LIBCLOUD-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997324#comment-13997324
]
Tomaz Muraus commented on LIBCLOUD-552:
---------------------------------------
To clear things up - Libcloud doesn't actually use cURL to perform HTTP
request. It uses Python's built in HTTP library.
In debug mode, cURL lines are printed so it's easier for the user to debug and
re-produce the requests.
So, there are potentially two issues here:
1. Actual issue in the Libcloud code. Can you please past the debug log and
code examples which re-produces this error.
2. Issue with the code which logs cURL lines for debugging purposes.
Edit: Yeah, you are right. As far as #2 goes, we should use "--head" flag. I
will make code modifications later today.
{code}
This option only changes the actual word used in the HTTP request, it does
not alter the way curl
behaves. So for example if you want to make a proper HEAD request, using -X
HEAD will not suffice.
You need to use the -I, --head option.
{code}
> CloudFiles CURL Request uses -X HEAD instead of --head or -I
> ------------------------------------------------------------
>
> Key: LIBCLOUD-552
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-552
> Project: Libcloud
> Issue Type: Improvement
> Components: Storage
> Affects Versions: 0.14.0-beta3
> Environment: Ubuntu 12.04.4 LTS
> curl 7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4
> libidn/1.23 librtmp/2.3
> Python 2.7.3 and Python 3.2.3
> Reporter: Brian Metzler
> Priority: Critical
>
> When running driver.container.download_object(), it attempts to get the
> metadata of the object by using 'curl -X HEAD', instead of 'curl -I' or 'curl
> --head'. curl does not properly handle HEAD requests with -X HEAD, as it
> still attempts to download the full file.
> Just turn on debugging, and check out the time it takes for a standard curl
> -I versus curl -X HEAD.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
