Re: Ranged PUTs, Content-Range, and Content-Length
On Tue, 30 Apr 2019 03:21:28 -0400 Ray Satiro via curl-library wrote: > CURLOPT_RANGE specifically as far as I know is only supposed to be > used for download, not upload (can anyone confirm?), which would > explain what you observed [1]. Anyway, I think what Amazon is doing > is unusual and you'd have to use CURLOPT_READFUNCTION and > CURLOPT_SEEKFUNCTION (adding in your offset) and set Content-Range > and amazon specific headers yourself. And yet, looking at the source code, there are explicit conditionals to check for CURLOPT_RANGE and turn it into a Content-Range header in an upload. So obviously this works, and not just by accident: someone intentionally took the time to write code that makes CURLOPT_RANGE (and CURLOPT_RESUME_FROM, for that matter) work for uploads as well. In current master (028126281901fb651819821f5c05caaf40976209), see the conditional in lib/http.c starting at line 2458. -- Christopher Head pgpX_AfvC_N0X.pgp Description: OpenPGP digital signature --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
Re: curl on docker hub
On Thu, May 2, 2019 at 8:09 AM James Fuller via curl-library wrote: > > update on curl docker - testing things on my fork here > https://github.com/xquery/curl-docker > and automation with travis > https://travis-ci.org/xquery/curl-docker > > which will also be responsible for pushing docker images to hub.docker.com > > seeking advice/thoughts on a few open questions: [...] > * what features to build as default is the biggest burning question > > orig poster (Olliver Schinagl) had suggested > > ./configure \ > --disable-ldap \ > --enable-ipv6 \ > --enable-unix-sockets \ > --prefix=/usr \ > --with-libssh2 \ > --with-nghttp2 \ > --with-pic \ > --with-ssl \ > --without-libidn \ > --without-libidn2 \ > > which seems specific to his needs. > > put another way - what features do we want enabled by default docker > image ... we could contemplate additional images that have 'all > features' enabled. You could consult the most recent curl survey (at https://daniel.haxx.se/media/curl-user-survey-2018-analysis.pdf) and set a simple threshold at e.g. 90% of users and pick the features that would be sufficient for such a fraction of users. You may need the raw data, since the graph in the survey result document doesn't specify whether a significant fraction of users use http/https plus another protocol such as ftp, sftp etc. Another interesting question would be which SSL backend you're going to use and how you keep the CA store up to date. rainer --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
