Revision tags: php-7.3.13RC1, php-7.2.26RC1, php-7.4.0, php-7.2.25, php-7.3.12, php-7.4.0RC6, php-7.3.12RC1, php-7.2.25RC1, php-7.4.0RC5, php-7.1.33, php-7.2.24, php-7.3.11, php-7.4.0RC4, php-7.3.11RC1, php-7.2.24RC1, php-7.4.0RC3, php-7.2.23, php-7.3.10, php-7.4.0RC2, php-7.2.23RC1, php-7.3.10RC1, php-7.4.0RC1, php-7.1.32, php-7.2.22, php-7.3.9, php-7.4.0beta4, php-7.2.22RC1, php-7.3.9RC1, php-7.4.0beta2, php-7.1.31, php-7.2.21, php-7.3.8, php-7.4.0beta1, php-7.2.21RC1, php-7.3.8RC1, php-7.4.0alpha3, php-7.3.7, php-7.2.20, php-7.4.0alpha2, php-7.3.7RC3, php-7.3.7RC2, php-7.2.20RC2, php-7.4.0alpha1, php-7.3.7RC1, php-7.2.20RC1, php-7.2.19, php-7.3.6, php-7.1.30, php-7.2.19RC1, php-7.3.6RC1, php-7.1.29, php-7.2.18, php-7.3.5 |
|
#
17a9f140 |
| 29-Apr-2019 |
Christoph M. Becker |
Extend CURLFile to support streams Due to former restrictions of the libcurl API, curl multipart/formdata file uploads supported only proper files. However, as of curl 7.56.0 the ne
Extend CURLFile to support streams Due to former restrictions of the libcurl API, curl multipart/formdata file uploads supported only proper files. However, as of curl 7.56.0 the new `curl_mime_*()` API is available (and already supported by PHP[1]), which allows us to support arbitrary *seekable* streams, which is generally desirable, and particularly resolves issues with the transparent Unicode and long part support on Windows (see bug #77711). Note that older curl versions are still supported, but CURLFile is still restricted to proper files in this case. [1] <http://git.php.net/?p=php-src.git;a=commit;h=a83b68ba56714bfa06737a61af795460caa4a105> (cherry picked from commit c68dc6b5e37e74d89e0a387079139c054c8faa81)
show more ...
|
Revision tags: php-7.2.18RC1, php-7.3.5RC1 |
|
#
e1202733 |
| 15-Apr-2019 |
Christoph M. Becker |
Use curl_mime_*() functions if available As of curl 7.56.0, `curl_formadd()` is deprecated in favor of `curl_mime_*()`, so we use the latter if available. (cherry picked from co
Use curl_mime_*() functions if available As of curl 7.56.0, `curl_formadd()` is deprecated in favor of `curl_mime_*()`, so we use the latter if available. (cherry picked from commit a83b68ba56714bfa06737a61af795460caa4a105)
show more ...
|
#
5d6e923d |
| 24-Sep-2019 |
Gabriel Caruso |
Remove mention of PHP major version in Copyright headers Closes GH-4732. |
#
4867864c |
| 18-Aug-2019 |
Simon Podlipsky |
Add Curl ext PHP stubs Closes GH-4557. |
#
429378d7 |
| 12-Aug-2019 |
Nikita Popov |
Remove some misleading RETURN_FALSE These functions throw, so they can't return false. This is just a subset... |
#
d59aac58 |
| 18-Jul-2019 |
Nikita Popov |
Report errors from stream read and write operations The php_stream_read() and php_stream_write() functions now return an ssize_t value, with negative results indicating failure. Function
Report errors from stream read and write operations The php_stream_read() and php_stream_write() functions now return an ssize_t value, with negative results indicating failure. Functions like fread() and fwrite() will return false in that case. As a special case, EWOULDBLOCK and EAGAIN on non-blocking streams should not be regarded as error conditions, and be reported as successful zero-length reads/writes instead. The handling of EINTR remains unclear and is internally inconsistent (e.g. some code-paths will automatically retry on EINTR, while some won't). I'm landing this now to make sure the stream wrapper ops API changes make it into 7.4 -- however, if the user-facing changes turn out to be problematic we have the option of clamping negative returns to zero in php_stream_read() and php_stream_write() to restore the old behavior in a relatively non-intrusive manner.
show more ...
|
#
be7f405f |
| 18-Jul-2019 |
Nikita Popov |
Merge branch 'PHP-7.3' into PHP-7.4
|
#
4a9f78f9 |
| 18-Jul-2019 |
Nikita Popov |
Merge branch 'PHP-7.2' into PHP-7.3
|
#
c8c183eb |
| 17-Jul-2019 |
Abyr Valg |
Fixed bug #77946 Save multi_info_read() result into easy handle. |
#
8757f30c |
| 25-Jun-2019 |
Nikita Popov |
Fix CURLINFO_COOKIELIST leak |
#
bc8fece0 |
| 12-Jun-2019 |
Nikita Popov |
Don't warn if libcurl SSL library not detected libcurl may link against 7 different ssl libraries, all of which are thread-safe -- apart from openssl, of course. We check for openssl
Don't warn if libcurl SSL library not detected libcurl may link against 7 different ssl libraries, all of which are thread-safe -- apart from openssl, of course. We check for openssl and register locking callbacks in that case, but we should not warn if any other library is used.
show more ...
|
#
5d333707 |
| 13-May-2019 |
GITSRC <34047788+gitsrc@users.noreply.github.com> |
Require semicolon after SAVE_CURL_ERROR() |
#
357da6bc |
| 13-May-2019 |
Christoph M. Becker |
Deprecate and ignore $version parameter of curl_version() `curl_version()`[1] (of ext/curl) makes `curl_version_info()`[2] (of libcurl) available to PHP userland. The latter requires to
Deprecate and ignore $version parameter of curl_version() `curl_version()`[1] (of ext/curl) makes `curl_version_info()`[2] (of libcurl) available to PHP userland. The latter requires to pass an `age` argument which usually is `CURLVERSION_NOW`, so that the information returned by the runtime matches the declarations used during compile time. For C programs it is simply necessary to pass this information, and in rare occasions it might make sense to pass something else than `CURLVERSION_NOW`. curl.h notes: | The 'CURLVERSION_NOW' is the symbolic name meant to be used by | basically all programs ever that want to get version information. For the PHP binding, using a newer `age` than available at compile time will neither provide the PHP program more information, nor would using an older `age` have tangible benefits. We therefore deprecate the useless `$version` parameter, and if it is passed nonetheless, we use `CURLVERSION_NOW` instead of the supplied value, and raise a warning. [1] <https://www.php.net/manual/en/function.curl-version.php> [2] <https://curl.haxx.se/libcurl/c/curl_version_info.html>
show more ...
|
#
2934f9da |
| 02-May-2019 |
Nikita Popov |
Merge branch 'PHP-7.3' into PHP-7.4
|
#
6b73e692 |
| 30-Apr-2019 |
Javier Spagnoletti |
Add more missing CURL_VERSION_* constants And also check for CURL_VERSION_* constants in the sync-constants.php script. Related to request #72189: Add missing `CURL_VERSION_*` c
Add more missing CURL_VERSION_* constants And also check for CURL_VERSION_* constants in the sync-constants.php script. Related to request #72189: Add missing `CURL_VERSION_*` constants.
show more ...
|
#
c68dc6b5 |
| 29-Apr-2019 |
Christoph M. Becker |
Extend CURLFile to support streams Due to former restrictions of the libcurl API, curl multipart/formdata file uploads supported only proper files. However, as of curl 7.56.0 the ne
Extend CURLFile to support streams Due to former restrictions of the libcurl API, curl multipart/formdata file uploads supported only proper files. However, as of curl 7.56.0 the new `curl_mime_*()` API is available (and already supported by PHP[1]), which allows us to support arbitrary *seekable* streams, which is generally desirable, and particularly resolves issues with the transparent Unicode and long part support on Windows (see bug #77711). Note that older curl versions are still supported, but CURLFile is still restricted to proper files in this case. [1] <http://git.php.net/?p=php-src.git;a=commit;h=a83b68ba56714bfa06737a61af795460caa4a105>
show more ...
|
#
a83b68ba |
| 15-Apr-2019 |
Christoph M. Becker |
Use curl_mime_*() functions if available As of curl 7.56.0, `curl_formadd()` is deprecated in favor of `curl_mime_*()`, so we use the latter if available. |
#
3e0f9c2c |
| 11-Apr-2019 |
Nikita Popov |
Remove curl gnutls locking This is only relevant for the gcrypt backend, which is no longer in use. I couldn't find any hard info on when exactly gcrypt support was dropped, but nett
Remove curl gnutls locking This is only relevant for the gcrypt backend, which is no longer in use. I couldn't find any hard info on when exactly gcrypt support was dropped, but nette is the default since 2.11.1. Most code that still has the gcrypt handling is checking against < 2.12. In either case, those versions were released in 2010/2011.
show more ...
|
#
539a16fd |
| 11-Apr-2019 |
Nikita Popov |
Avoid curl ssl callback warnings with OpenSSL 1.1 |
Revision tags: php-7.2.17, php-7.3.4, php-7.1.28, php-7.3.4RC1, php-7.2.17RC1 |
|
#
d9d253fa |
| 06-Mar-2019 |
Daniel Stenberg |
curl_exec: remove bad check for CURLE_PARTIAL_FILE This check introduced in 2004 is wrong and removed. A HEAD request with curl does *not* cause this error code - only if you make a regu
curl_exec: remove bad check for CURLE_PARTIAL_FILE This check introduced in 2004 is wrong and removed. A HEAD request with curl does *not* cause this error code - only if you make a regular GET request but tell curl to send a HEAD using CURLOPT_CUSTOMREQUEST and then you've asked for it. You do a proper HEAD request with curl by setting the CURLOPT_NOBODY option to 1L. This was the case in 2004. This is still the case in 2019. This is also documented in libcurl documentation. This check hides the possibly serious error when this error code is genuinely and correctly returned by curl because the transfer was truncated and ended up partial. As can be seen, I objected to this change already in the original bug: https://bugs.php.net/bug.php?id=27341
show more ...
|
Revision tags: php-7.1.27, php-7.3.3, php-7.2.16 |
|
#
6878d102 |
| 01-Mar-2019 |
Nikita Popov |
Merge branch 'PHP-7.3' into PHP-7.4
|
#
8be12e77 |
| 01-Mar-2019 |
Nikita Popov |
Merge branch 'PHP-7.2' into PHP-7.3
|
#
5025eb05 |
| 01-Mar-2019 |
Jay Satiro |
curl_error: return an empty string if no error occurred CURLOPT_ERRORBUFFER doc says "Do not rely on the contents of the buffer unless an error code was returned." [1] Prior to
curl_error: return an empty string if no error occurred CURLOPT_ERRORBUFFER doc says "Do not rely on the contents of the buffer unless an error code was returned." [1] Prior to this change the error buffer was returned even if no error had occurred, and that buffer may contain incorrect information in such a case. [2] [1]: https://curl.haxx.se/libcurl/c/CURLOPT_ERRORBUFFER.html [2]: https://github.com/curl/curl/issues/3629
show more ...
|
Revision tags: php-7.3.3RC1, php-7.2.16RC1, php-7.2.15, php-7.3.2, php-7.2.15RC1 |
|
#
92ac598a |
| 22-Jan-2019 |
Peter Kokot |
Remove local variables This patch removes the so called local variables defined per file basis for certain editors to properly show tab width, and similar settings. These are mainly
Remove local variables This patch removes the so called local variables defined per file basis for certain editors to properly show tab width, and similar settings. These are mainly used by Vim and Emacs editors yet with recent changes the once working definitions don't work anymore in Vim without custom plugins or additional configuration. Neither are these settings synced across the PHP code base. A simpler and better approach is EditorConfig and fixing code using some code style fixing tools in the future instead. This patch also removes the so called modelines for Vim. Modelines allow Vim editor specifically to set some editor configuration such as syntax highlighting, indentation style and tab width to be set in the first line or the last 5 lines per file basis. Since the php test files have syntax highlighting already set in most editors properly and EditorConfig takes care of the indentation settings, this patch removes these as well for the Vim 6.0 and newer versions. With the removal of local variables for certain editors such as Emacs and Vim, the footer is also probably not needed anymore when creating extensions using ext_skel.php script. Additionally, Vim modelines for setting php syntax and some editor settings has been removed from some *.phpt files. All these are mostly not relevant for phpt files neither work properly in the middle of the file.
show more ...
|
#
0cf7de1c |
| 30-Jan-2019 |
Zeev Suraski |
Remove yearly range from copyright notice |