delta/php-git.git/ext/curl, branch php-7.2.20 git.php.net: repository/php-src.git Fix test regarding Unix Domain Sockets on Windows 2019-06-06T12:59:58+00:00 Christoph M. Becker cmbecker69@gmx.de 2019-06-06T12:56:47+00:00 2df32942d3ec9b70e791225aeee70a857b9b292e Recent Windows versions actually support Unix Domain Sockets. Cf. <https://github.com/curl/curl/pull/3939>. 
Recent Windows versions actually support Unix Domain Sockets.  Cf.
<https://github.com/curl/curl/pull/3939>.
Fix test case for cURL 7.65.0 2019-05-22T10:01:23+00:00 Christoph M. Becker cmbecker69@gmx.de 2019-05-22T10:00:06+00:00 62fe6ba20c229bb6ffd910f1b494a310c950cef6 Reported and patch provided by @Jan-E. 
Reported and patch provided by @Jan-E.
Fix precedence issue causing sub-second timeouts to be 0 in 2019-05-21T21:44:11+00:00 Rasmus Lerdorf rasmus@lerdorf.com 2019-05-21T21:44:11+00:00 7b42cdf95ee91b723e7df51ac96f880de51f4591 curl_multi_select 
curl_multi_select
Added test for #77535 fix 2019-03-15T18:11:51+00:00 Pedro Magalhães pmmaga@php.net 2019-03-15T18:11:51+00:00 f167b06d4c86c96291c21c027ba3cae22f5b5be8 






Don't immediately destroy curl pushfunction
2019-03-15T16:07:19+00:00

Nikita Popov
nikita.ppv@gmail.com

2019-03-15T16:06:34+00:00

97f9fd6949a52d1eb30c3e1c90f0789b57c29468












curl_error: return an empty string if no error occurred
2019-03-01T13:54:37+00:00

Jay Satiro
raysatiro@yahoo.com

2019-03-01T06:37:00+00:00

5025eb05bde83a0a51eb0668c45c240b366545bf

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





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







Sync test with changes in libcurl 7.64.0
2019-02-08T06:22:38+00:00

Anatol Belski
ab@php.net

2019-02-08T06:22:38+00:00

e27301c7b37f6a1643a0dc1966919bd62a32bc74












Sync test for libcurl 7.64.0
2019-02-08T06:21:59+00:00

Anatol Belski
ab@php.net

2019-02-08T06:21:59+00:00

c9f0e12353462585f7ebdc193a85dca96a055697












Fixed bug #76675
2019-01-18T11:04:25+00:00

Pedro Magalhães
pmmaga@php.net

2019-01-16T00:33:03+00:00

32ae7160377e9548dcf27ff3e0e75c3c9cd3c36c

Leave a reference to the resource in the php_curl.





Leave a reference to the resource in the php_curl.







Sync leading and final newlines in *.phpt sections
2018-10-15T02:31:31+00:00

Peter Kokot
peterkokot@gmail.com

2018-10-15T02:31:31+00:00

f1d7e3ca0b70f910fcecef0278de9c15440ca3c0

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

According to POSIX, a line is a sequence of zero or more non-' <newline>'
characters plus a terminating '<newline>' character. [1] Files should
normally have at least one final newline character.

C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."

Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2





This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

According to POSIX, a line is a sequence of zero or more non-' <newline>'
characters plus a terminating '<newline>' character. [1] Files should
normally have at least one final newline character.

C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."

Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2