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: CURLE_BAD_FUNCTION_ARGUMENT for invalid response header filed

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

From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Tue, 28 Feb 2023 09:17:54 +0100 (CET)

On Tue, 28 Feb 2023, bhavesh soni via curl-users wrote:

> Debugging respone header, I could see indeed there is an "additional" HTTP
> response code in the header fields without a colon (:). Probably that's the
> reason cURL is invalidating the response with "curl: (43) A libcurl
> function was given a bad argument".

Possibly, yes. You did not by any chance follow redirects so that is just a
second response we see?

We don't really have enough information to tell what happens.

> Is there anyway, I can modify cURL source code at my end building custom
> curl to link with?

Sure, you can patch out that check and allow invalid HTTP. It's just code. You
can make it do anything you want.

-- 
  / daniel.haxx.se
  | Commercial curl support up to 24x7 is available!
  | Private help, bug fixes, support, ports, new features
  | https://curl.se/support.html
-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users
Etiquette:   https://curl.se/mail/etiquette.html

Received on 2023-02-28

This message: [ Message body ]
Previous message: bhavesh soni via curl-users: "CURLE_BAD_FUNCTION_ARGUMENT for invalid response header filed"
In reply to: bhavesh soni via curl-users: "CURLE_BAD_FUNCTION_ARGUMENT for invalid response header filed"

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