On Fri, Jan 1, 2021 at 10:08 AM René Berber via curl-library
wrote:
>
> On 12/31/2020 6:14 PM, Hongyi Zhao via curl-library wrote:
>
> > On Fri, Jan 1, 2021 at 7:51 AM Daniel Stenberg wrote:
> >>
> >> On Thu, 31 Dec 2020, Hongyi Zhao via curl-library wrote:
> >>
> >>> I only see the RTSP
On 12/31/2020 6:14 PM, Hongyi Zhao via curl-library wrote:
On Fri, Jan 1, 2021 at 7:51 AM Daniel Stenberg wrote:
On Thu, 31 Dec 2020, Hongyi Zhao via curl-library wrote:
I only see the RTSP protocol is supported by libcurl, but for streaming
media relative protocols, I also learned that
On Fri, Jan 1, 2021 at 7:51 AM Daniel Stenberg wrote:
>
> On Thu, 31 Dec 2020, Hongyi Zhao via curl-library wrote:
>
> > I only see the RTSP protocol is supported by libcurl, but for streaming
> > media relative protocols, I also learned that the RTP/RTCP/RTSP protocols
> > are all needed to
On Thu, 31 Dec 2020, Hongyi Zhao via curl-library wrote:
I only see the RTSP protocol is supported by libcurl, but for streaming
media relative protocols, I also learned that the RTP/RTCP/RTSP protocols
are all needed to co-operate for complete the whole job.
Out of those three, only RTSP is
---
In response to:
---
Okay, this has been discussed before
(https://github.com/curl/curl/issues/3192) and is deemed
by-design for compatibility reasons.
I guess Amazon returning gzipped data regardless of the
request headers is new (but not, in itself, erroneous).
On 31/12/2020 16:56, Tomalak Geret'kal via curl-library wrote:
> Okay, this has been discussed before
> (https://github.com/curl/curl/issues/3192) and is deemed
> by-design for compatibility reasons.
>
> I guess Amazon returning gzipped data regardless of the
> request headers is new (but not, in
On 31/12/2020 16:54, Tomalak Geret'kal wrote:
> On 31/12/2020 16:52, Tomalak Geret'kal wrote:
>> Per the headers, it's gzip-encoded. If you output to
>> out.html.gzip, then unzip, it'll be fine.
>>
>> I don't know why this just happened. I would have thought
>> curl would auto decode the contents
On 31/12/2020 16:52, Tomalak Geret'kal wrote:
> Per the headers, it's gzip-encoded. If you output to
> out.html.gzip, then unzip, it'll be fine.
>
> I don't know why this just happened. I would have thought
> curl would auto decode the contents to be honest.
>
> curl 7.29.0
On 31/12/2020 16:30, Mac-Fly via curl-library wrote:
> Dear all,
>
> amazon.com was working just fine with cURL until
> yesterday. When I issue:
>
> curl.exe -A "Mozilla/5.0 (Windows NT 6.1; Win64; x64;
> rv:59.0)
> Gecko/20100101 Firefox/59.0" https://www.amazon.com -o
> "out.html"
>
> ...I get
Dear all,
amazon.com was working just fine with cURL until yesterday. When I issue:
curl.exe -A "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0)
Gecko/20100101 Firefox/59.0" https://www.amazon.com -o "out.html"
...I get binary garbage in the "out.html" file.
Note that I even tried to "hide"
Hi,
I noticed the following description on the curl's GitHub repo:
A command line tool and library for transferring data with URL syntax,
supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP,
IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP,
SMB, SMBS, SMTP,
11 matches
Mail list logo
