NAME

CURLOPT_KEEP_SENDING_ON_ERROR - keep sending on early HTTP response >= 300

SYNOPSIS

#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_KEEP_SENDING_ON_ERROR, long keep_sending);

DESCRIPTION

A long parameter set to 1 tells the library to keep sending the request body if the HTTP code returned is equal to or larger than 300. The default action would be to stop sending and close the stream or connection.
 
This option is suitable for manual NTLM authentication, i.e. if an application does not use CURLOPT_HTTPAUTH(3), but instead sets "Authorization: NTLM ..." headers manually using CURLOPT_HTTPHEADER(3).
 
Most applications do not need this option.

DEFAULT

0, stop sending on error

PROTOCOLS

HTTP

EXAMPLE

CURL *curl = curl_easy_init();
if(curl) {
  CURLcode ret;
  curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/");
  curl_easy_setopt(curl, CURLOPT_POSTFIELDS, "sending data");
  curl_easy_setopt(curl, CURLOPT_KEEP_SENDING_ON_ERROR, 1L);
  ret = curl_easy_perform(curl);
}

AVAILABILITY

Along with HTTP. Added in 7.51.0.

RETURN VALUE

Returns CURLE_OK if HTTP is enabled, and CURLE_UNKNOWN_OPTION if not.

SEE ALSO

CURLOPT_FAILONERROR(3), CURLOPT_HTTPHEADER(3),

Recommended readings

Pages related to CURLOPT_KEEP_SENDING_ON_ERROR you should read also:

Questions & Answers

Helpful answers and articles about CURLOPT_KEEP_SENDING_ON_ERROR you may found on these sites:
Stack Overflow Server Fault Super User Unix & Linux Ask Ubuntu Network Engineering DevOps Raspberry Pi Webmasters Google Search