#34545 [Bgs]: TIMECOND_IFMODSINCE not implemented for many years???

ID: 34545 User updated by: mshonich at yandex dot ru Reported By: mshonich at yandex dot ru Status: Bogus Bug Type: cURL related Operating System: any PHP Version: 4.4.0 New Comment: So, is it all about documentation being incorrect once (no "CURL_" prefix before TIMECOND_IFMODSINCE) or twice (also default behaviour is not TIMECODE_IFMODSINCE as it is described)? If so, better move this bug to "docs" cathegory. Previous Comments: ------------------------------------------------------------------------ [2005-09-19 08:27:43] sniper@php.net I don't know what version you actually have tried, but CURL_TIMECOND_IFMODSINCE has existed since 4.3.9.. ------------------------------------------------------------------------ [2005-09-19 01:28:45] mshonich at yandex dot ru Description: ------------ Docs `bout curl_setopt notice the CURLOPT_TIMECOND and CURLOPT_TIMEVALUE options. Specifically: <i>CURLOPT_TIMEVALUE: Pass a long as a parameter that is the time in seconds since January 1st, 1970. The time will be used as specified by the CURLOPT_TIMEVALUE option, or by default the TIMECOND_IFMODSINCE will be used. </i> First of all, documentation is confusing: IMHO it should be read <i>The time will be used as specified by the CURLOPT_TIMECOND option, or by default the TIMECOND_IFMODSINCE will be used. </i> Second, it is completely wrong: If you only specify CURLOPT_TIMEVALUE without CURLOPT_TIMECOND, then nothing will happen - If-Modified-Since header won't be send. Thus default behaviour is not TIMECOND_IFMODSINCE. Next big thing about this bug is that TIMECOND_IFMODSINCE was never defined for astonishing high number of major releases. One can use curl_setopt(CURLOPT_TIMECOND, 1) as a workaround, but it is darn unconvient. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=34545&edit=1