-------- Исходное сообщение --------
Тема: curl-library Digest, Vol 164, Issue 28
От: curl-library-request@cool.haxx.se
Кому: curl-library@cool.haxx.se
Копия:

Send curl-library mailing list submissions to
curl-library@cool.haxx.se

To subscribe or unsubscribe via the World Wide Web, visit
https://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library
or, via email, send a message with subject or body 'help' to
curl-library-request@cool.haxx.se

You can reach the person managing the list at
curl-library-owner@cool.haxx.se

When replying, please edit your Subject line so it is more specific
than "Re: Contents of curl-library digest..."


Today's Topics:

1. Libcurl (Татьяна Комиссарова)
2. Re: Libcurl (Igor Korot)
3. Re: Libcurl (Daniel Stenberg)
4. Re: Ranged PUTs, Content-Range, and Content-Length (Ray Satiro)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 Apr 2019 21:36:12 +0300
From: Татьяна Комиссарова
To: "curl-library@cool.haxx.se"
Subject: Libcurl
Message-ID:
<-k48tm4d8k49k-m0tv6-kary7zryz1mo-9ta0oohgydnz-8a7k5sfsgyn3-hfjvfk-z1wb7q71ro6bakz9m0x28k24-r22jdxmpc4c2-jonqk8mqb9edx8tuuj-b6x7sv-nqiqsv-5z39vi99rw2po5an6k.1556562972346@email.android.com>

Content-Type: text/plain; charset=utf-8


Hi. Help, please, to collect Curl library. I downloaded the latest version, but I do not know what to do next. Thank you for help



------------------------------

Message: 2
Date: Mon, 29 Apr 2019 16:09:53 -0500
From: Igor Korot
To: libcurl development
Cc: Татьяна Комиссарова
Subject: Re: Libcurl
Message-ID:

Content-Type: text/plain; charset="UTF-8"

Hi,

On Mon, Apr 29, 2019 at 2:54 PM Татьяна Комиссарова via curl-library
wrote:
>
>
> Hi. Help, please, to collect Curl library. I downloaded the latest version, but I do not know what to do next. Thank you for help

What is you task?
What are you suppose to do?

Thank you.

>
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html



------------------------------

Message: 3
Date: Mon, 29 Apr 2019 23:12:31 +0200 (CEST)
From: Daniel Stenberg
To: Татьяна Комиссарова via curl-library

Cc: Татьяна Комиссарова
Subject: Re: Libcurl
Message-ID:
Content-Type: text/plain; charset="utf-8"; Format="flowed"

On Mon, 29 Apr 2019, Татьяна Комиссарова via curl-library wrote:

> Hi. Help, please, to collect Curl library. I downloaded the latest version,
> but I do not know what to do next. Thank you for help

You need to explain more what exactly you did and what you want!

You downloaded what? The source code and now you want to build and install it?

Or did you download a package/pre-built binary and have a problem to install
it?

Which operating system are you working with?

For a "getting started" guide on libcurl basics, I think everything curl's
chapter here is a good start: https://ec.haxx.se/libcurl.html

--

/ daniel.haxx.se

------------------------------

Message: 4
Date: Tue, 30 Apr 2019 03:21:28 -0400
From: Ray Satiro
To: curl-library@cool.haxx.se
Subject: Re: Ranged PUTs, Content-Range, and Content-Length
Message-ID:
Content-Type: text/plain; charset="utf-8"

On 4/28/2019 9:47 PM, Christopher Head via curl-library wrote:
> On Sun, 28 Apr 2019 16:57:39 -0400
> Ray Satiro via curl-library wrote:
>
>> That's not allowed. To PUT is to completely replace a resource.
> Then it seems that upload resuming, which libcurl does support, ought
> to be banned, too, oughtn’t it? After all, using Content-Range to
> resume an interrupted upload is modifying the existing resource by
> appending more bytes on the end, not replacing a resource wholesale.
> Yet upload resuming using Content-Range seems not to be all that
> uncommon (at least, searching this list’s archives showed a few results
> of people doing this in the past, and CURLOPT_RESUME_FROM does apply to
> PUTs’ request bodies).
>
> In my defense, I’m not the one who decided to use PUT this way. Amazon
> did [1], and I’m just following their rules.
>
> If this is sufficiently weird, I certainly don’t mind using
> CURLOPT_HTTPHEADER. I just wanted to check if I was missing something
> that would allow this to be done in a nicer way.
>
> [1]
> https://docs.aws.amazon.com/amazonglacier/latest/dev/api-upload-part.html


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.


[1]: https://curl.haxx.se/mail/lib-2019-04/0075.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL:

------------------------------

Subject: Digest Footer

_______________________________________________
curl-library mailing list
curl-library@cool.haxx.se
https://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library


------------------------------

End of curl-library Digest, Vol 164, Issue 28
*********************************************