From 54ecc11cc4c4cf4a6ed958fd2906f3a791d1c8d2 Mon Sep 17 00:00:00 2001 From: Kwon-Young Choi Date: Sat, 4 Apr 2020 17:27:18 +0200 Subject: CURLINFO_CONDITION_UNMET: return true for 304 http status code In libcurl, CURLINFO_CONDITION_UNMET is used to avoid writing to the output file if the server did not transfered a file based on time condition. In the same manner, getting a 304 HTTP response back from the server, for example after passing a custom If-Match-* header, also fulfill this condition. Fixes #5181 Closes #5183 --- docs/libcurl/opts/CURLINFO_CONDITION_UNMET.3 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/libcurl/opts') diff --git a/docs/libcurl/opts/CURLINFO_CONDITION_UNMET.3 b/docs/libcurl/opts/CURLINFO_CONDITION_UNMET.3 index 27488656e..78c28fa02 100644 --- a/docs/libcurl/opts/CURLINFO_CONDITION_UNMET.3 +++ b/docs/libcurl/opts/CURLINFO_CONDITION_UNMET.3 @@ -22,7 +22,7 @@ .\" .TH CURLINFO_CONDITION_UNMET 3 "1 Sep 2015" "libcurl 7.44.0" "curl_easy_getinfo options" .SH NAME -CURLINFO_CONDITION_UNMET \- get info on unmet time conditional +CURLINFO_CONDITION_UNMET \- get info on unmet time conditional or 304 HTTP response. .SH SYNOPSIS #include @@ -32,7 +32,9 @@ Pass a pointer to a long to receive the number 1 if the condition provided in the previous request didn't match (see \fICURLOPT_TIMECONDITION(3)\fP). Alas, if this returns a 1 you know that the reason you didn't get data in return is because it didn't fulfill the condition. The long this argument points to will -get a zero stored if the condition instead was met. +get a zero stored if the condition instead was met. This can also return 1 if +the server responded with a 304 HTTP status code, for example after sending a +custom "If-Match-*" header. .SH PROTOCOLS HTTP and some .SH EXAMPLE -- cgit v1.2.3