curl / Mailing Lists / curl-users / Single Mail

Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: Why data still can be downloaded with HTTP 403 status?

From: Dan Fandrich via curl-users <curl-users_at_cool.haxx.se>
Date: Sun, 10 May 2020 23:21:41 +0200

Please don't reply to an unrelated message to start a new topic. It breaks
threading.

On Sun, May 10, 2020 at 01:56:54PM -0500, Peng Yu via curl-users wrote:
> $ curl --verbose ...
> ...
> < HTTP/1.1 403 Forbidden
> ...
> <
> { [359 bytes data]
> 100 81498 0 81498 0 0 50214 0 --:--:-- 0:00:01 --:--:-- 50183
>
> When the above 403 code occurs, curl still can download the data. But
> wget just gives up. I don't understand why curl behaves differently
> from wget. Could anybody help me understand why curl can still
> download the content with the 403 status code? Thanks.

A server can still return data with a 403 response. curl merely returns that
data.
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-05-10

This message: [ Message body ]
Next message: Jeremy Nicoll via curl-users: "Re: «--etag-compare» while «--continue-at»"
Previous message: Peng Yu via curl-users: "Why data still can be downloaded with HTTP 403 status?"
In reply to: Peng Yu via curl-users: "Why data still can be downloaded with HTTP 403 status?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]