Doc #76328 [Ver->Csd]: Documentation of CURLINFO_HTTP_CODE as legacy

Edit report at https://bugs.php.net/bug.php?id=76328&edit=1 ID: 76328 Updated by: cmb@php.net Reported by: ssimo3 at lsuhsc dot edu Summary: Documentation of CURLINFO_HTTP_CODE as legacy -Status: Verified +Status: Closed Type: Documentation Problem Package: cURL related PHP Version: 5.6.36 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2018-05-11 16:11:32] cmb@php.net Automatic comment from SVN on behalf of cmb Revision: http://svn.php.net/viewvc/?view=revision&revision=345002 Log: Fix #76328: Documentation of CURLINFO_HTTP_CODE as legacy ------------------------------------------------------------------------ [2018-05-11 15:22:47] requinix@php.net https://curl.haxx.se/libcurl/c/CURLINFO_RESPONSE_CODE.html > This option was previously known as CURLINFO_HTTP_CODE in libcurl 7.10.7 and earlier. ------------------------------------------------------------------------ [2018-05-11 13:59:19] ssimo3 at lsuhsc dot edu Description: ------------ --- From manual page: http://www.php.net/function.curl-getinfo --- I believe that whoever documented the change to curlinfo in PHP 5.5, i.e., added CURLINFO_RESPONSE_CODE, forgot to state "(Legacy - from PHP 5.5 onward, use CURLINFO_RESPONSE_CODE instead)" after the definition of CURLINFO_HTTP_CODE. I do not have any code which does not contain secret credentials which demonstrates that they are the same. Nonetheless, even in the most obscure of response codes, they appear to change in lockstep. Thank you! Stuart Simon ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=76328&edit=1