stream_get_line() could contain the delimiter string if that string
had more than one character. The bug manifested itself when a read on
the stream ended with part of the delimiter string and the read after
would start with the rest of the delimiter string; provided that
the data of first read did not complete the max length result of the
call to stream_get_line() with the partial delimiter used in that max
length return. In that case, the delimiter will still appear in
the result, divided in two subsequent return values. That is not a bug.
See <http://www.mail-archive.com/internals@lists.php.net/msg61325.html>
* 'PHP-5.3' of git.php.net:php-src: (29 commits)
Correct the test summary
Fixed bug #60723 (error_log error time has changed to UTC ignoring default timezo)
Avoid calling select if maxfd returned by curl_multi_fdset is -1
Fixed bug #63111 (is_callable() lies for abstract static method)
updated lib versions
Fixed bug #61442 (exception threw in __autoload can not be catched)
updated libary versions
split tests for the new zlib version on win
Fixed Bug #63103 (ext\curl\tests\bug62839.phpt broken)
test should fail
Fixed bug #63093 (Segfault while load extension failed in zts-build).
Add XFAIL test for bug #62852
Revert "Fixed bug #62852 (Unserialize invalid DateTime causes crash)"
Change package.xml fix description
Fixed bug #60901 (Improve "tail" syntax for AIX installation)
This will become 5.3.18
Update RELEASE PROCESS
fix NEWS after releses
Fix doc bug #63032 (Number of release in documentation).
- Fixed bug #61767 (Shutdown functions not called in certain error situation) - Fixed bug #60909 (custom error handler throwing Exception + fatal error = no shutdown function)
...
As per libcurl documentation :
When libcurl returns -1 in max_fd, it is because libcurl currently
does something that isn't possible for your application to monitor
with a socket and unfortunately you can then not know exactly when
the current action is completed using select().
