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: HTTP status and error codes
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: R C via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 4 Apr 2024 16:00:58 -0600
ah, alright,
thanks,
Ron
On 4/4/24 15:34, Daniel Stenberg wrote:
> On Thu, 4 Apr 2024, R C via curl-library wrote:
>
>> I can read the HTTP status with CURLINFO_RESPONSE_CODE, can the
>> actual status/error message also be printed? (are the messages
>> available in libcurl?
>
> There is no way to get the so called "reason-phrase" using the API,
> no. You can extract it yourself using the header callback if you truly
> want to.
>
> RFC 9112 says this:
>
> A client SHOULD ignore the reason-phrase content because it is not a
> reliable channel for information
>
> HTTP/2 and HTTP/3 dropped the reason phrase completely from the
> protocol for that reason.
>
Date: Thu, 4 Apr 2024 16:00:58 -0600
ah, alright,
thanks,
Ron
On 4/4/24 15:34, Daniel Stenberg wrote:
> On Thu, 4 Apr 2024, R C via curl-library wrote:
>
>> I can read the HTTP status with CURLINFO_RESPONSE_CODE, can the
>> actual status/error message also be printed? (are the messages
>> available in libcurl?
>
> There is no way to get the so called "reason-phrase" using the API,
> no. You can extract it yourself using the header callback if you truly
> want to.
>
> RFC 9112 says this:
>
> A client SHOULD ignore the reason-phrase content because it is not a
> reliable channel for information
>
> HTTP/2 and HTTP/3 dropped the reason phrase completely from the
> protocol for that reason.
>
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-04-05