summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * 7.3.28 is nextChristoph M. Becker2021-02-024-7/+9
| |
* | Update year to 2021Peter Kokot2021-02-028-8/+8
| | | | | | | | Closes GH-6636.
* | Add missing derefs in CurlFileNikita Popov2021-02-021-0/+3
| | | | | | | | As pointed out on GH-6456.
* | Fix persistent leak on load_wsdl_ex failureNikita Popov2021-02-021-2/+1
| | | | | | | | | | | | Move the load_wsdl_ex call into the zend_try that destroys the docs hash table. The wsdl will be inserted into docs early on, and will thus be released on subsequent bailout.
* | Merge branch 'PHP-7.3' into PHP-7.4Christoph M. Becker2021-02-010-0/+0
|\ \ | |/ | | | | | | * PHP-7.3: Revert "Updated to version 2021.1 (2021a)"
| * Revert "Updated to version 2021.1 (2021a)"Christoph M. Becker2021-02-011-2559/+2360
| | | | | | | | | | This reverts commit 491488d21707062fa8e9b9187db3585fb0d347da, since PHP-7.3 is in security mode, and this does not look security related.
* | Fix #80654: file_get_contents() maxlen fails above (2**31)-1 bytesChristoph M. Becker2021-02-013-8/+4
| | | | | | | | | | | | | | | | | | We remove the arbitrary restriction to `INT_MAX`; it is superfluous on 32bit systems where `ZEND_LONG_MAX == INT_MAX` anyway, and not useful on 64bit systems, where larger files should be readable, if the `memory_limit` is large enough. Closes GH-6648.
* | Fix Laravel build on community jobNikita Popov2021-02-011-4/+4
| | | | | | | | Now requires PHP 7.4, so use php7.4 to run composer everywhere.
* | Fix buildNikita Popov2021-02-011-1/+1
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-314-14/+37
|\ \ | |/ | | | | | | * PHP-7.3: Fix bug #80672 - Null Dereference in SoapClient
| * Fix bug #80672 - Null Dereference in SoapClientStanislav Malyshev2021-01-315-14/+40
| |
* | NEWSRemi Collet2021-01-281-0/+3
| |
* | Fix #80682 opcache doesn't honour pcre.jit optionRemi Collet2021-01-281-4/+6
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-271-16/+0
|\ \ | |/ | | | | | | * PHP-7.3: Rm unneeded function
| * Rm unneeded functionStanislav Malyshev2021-01-271-16/+0
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-268-28/+38
|\ \ | |/ | | | | | | * PHP-7.3: Alternative fix for bug 77423
| * Alternative fix for bug 77423Christoph M. Becker2021-01-268-28/+38
| | | | | | | | | | | | | | | | | | | | | | That bug report originally was about `parse_url()` misbehaving, but the security aspect was actually only regarding `FILTER_VALIDATE_URL`. Since the changes to `parse_url_ex()` apparently affect userland code which is relying on the sloppy URL parsing[1], this alternative restores the old parsing behavior, but ensures that the userinfo is checked for correctness for `FILTER_VALIDATE_URL`. [1] <https://github.com/php/php-src/commit/5174de7cd33c3d4fa591c9c93859ff9989b07e8c#commitcomment-45967652>
* | Fix #70091: Phar does not mark UTF-8 filenames in ZIP archivesChristoph M. Becker2021-01-263-0/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The default encoding of filenames in a ZIP archive is IBM Code Page 437. Phar, however, only supports UTF-8 filenames. Therefore we have to mark filenames as being stored in UTF-8 by setting the general purpose bit 11 (the language encoding flag). The effect of not setting this bit for non ASCII filenames can be seen in popular tools like 7-Zip and UnZip, but not when extracting the archives via ext/phar (which is agnostic to the filename encoding), or via ext/zip (which guesses the encoding). Thus we add a somewhat brittle low-level test case. Closes GH-6630.
* | Update versionChristoph M. Becker2021-01-261-3/+3
| | | | | | | | That appears to have been forgotten for a while.
* | Fix #75850: Unclear error message wrt. __halt_compiler() w/o semicolonChristoph M. Becker2021-01-253-2/+6
| | | | | | | | | | | | We add the failure reason to the error message. Closes GH-6638.
* | Updated to version 2021.1 (2021a)Derick Rethans2021-01-251-2360/+2559
| |
* | Empty mergeDerick Rethans2021-01-250-0/+0
|\ \ | |/
| * Updated to version 2021.1 (2021a)Derick Rethans2021-01-251-2360/+2559
| |
* | Add missing SKIPIF clause for recently introduced test caseChristoph M. Becker2021-01-211-0/+1
| |
* | Fix #80648: Fix for bug 79296 should be based on runtime versionChristoph M. Becker2021-01-202-5/+10
| | | | | | | | | | | | | | Instead of checking for actually affected libzip versions, we now always `ZIP_TRUNCATE` empty files unless `ZIP_RDONLY` is set. Closes GH-6625.
* | Add missing SKIPIF clauses to new test casesChristoph M. Becker2021-01-202-0/+2
| |
* | Update NEWS and versionDerick Rethans2021-01-192-2/+4
| |
* | Update NEWS for PHP 7.4.15RC1Derick Rethans2021-01-191-1/+1
| |
* | Fixed bug #42560sj-i2021-01-196-10/+37
| | | | | | | | | | | | | | | | | | | | | | | | Check open_basedir after the fallback to the system's temporary directory in tempnam(). In order to preserve the current behavior of upload_tmp_dir (do not check explicitly specified dir, but check fallback), new flags are added to check open_basedir for explicit dir and for fallback. Closes GH-6526.
* | Fix #69279: Compressed ZIP Phar extractTo() creates garbage filesChristoph M. Becker2021-01-196-1/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When extracting compressed files from an uncompressed Phar, we must not use the direct file pointer, but rather get an uncompressed file pointer. We also add a test to show that deflated and stored entries are properly extracted. This also fixes #79912, which appears to be a duplicate of #69279. Co-authored-by: Anna Filina <afilina@gmail.com> Closes GH-6599.
* | Fix #80595: Resetting POSTFIELDS to empty array breaks requestChristoph M. Becker2021-01-184-2/+43
| | | | | | | | | | | | | | | | | | | | | | | | This is mainly to work around https://github.com/curl/curl/issues/6455, but not building the mime structure for empty hashtables is a general performance optimization, so we do not restrict it to affected cURL versions (7.56.0 to 7.75.0). The minor change to bug79033.phpt is unexpected, but should not matter in practice. Closes GH-6606.
* | Revert "Fix #76813: Access violation near NULL on source operand"Christoph M. Becker2021-01-114-24/+3
| | | | | | | | | | This reverts commit 5e15c9c41f8318a8392c2e2c78544f218736549c, since re2c default rules are only available as of re2c 0.13.7.
* | Avoid modifying the return value of readline_completion_function()Christoph M. Becker2021-01-071-0/+1
| | | | | | | | | | | | | | | | | | The internal function `_readline_command_generator()` modifies the internal array pointer of `readline_completion_function()`'s return value. We therefore separate the array, what also avoids failing assertions regarding the array refcount. Closes GH-6582.
* | Fix #77565: Incorrect locator detection in ZIP-based pharsChristoph M. Becker2021-01-056-40/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We must not assume that the first end of central dir signature in a ZIP archive actually designates the end of central directory record, since the data in the archive may contain arbitrary byte patterns. Thus, we better search from the end of the data, what is also slightly more efficient. There is, however, no way to detect the end of central directory signature by searching from the end of the ZIP archive with absolute certainty, since the signature could be part of the trailing comment. To mitigate, we check that the comment length fits to the found position, but that might still not be the correct position in rare cases. Closes GH-6507.
* | Fix memory leak in Phar::webPhar() on WindowsChristoph M. Becker2021-01-051-19/+17
| | | | | | | | Closes GH-6574.
* | gdbinit: use ____print_str to print htable keysDylan K. Taylor2021-01-051-1/+2
| | | | | | | | | | | | | | | | | | I noticed this problem while dumping the contents of EG(function_table), where keys for closures start with a null byte. printf interprets this as a zero-length string and emits nothing. This allows the key to be rendered properly in readable form. Closes GH-6577.
* | Disable non-cron travis jobsNikita Popov2021-01-041-0/+3
| | | | | | | | | | This was already done for PHP-8.0 and master, do it for PHP-7.4 as well.
* | [ci skip] Update NEWSStanislav Malyshev2021-01-041-0/+2
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-040-0/+0
|\ \ | |/ | | | | | | * PHP-7.3: [ci skip] Fix order
| * [ci skip] Fix orderStanislav Malyshev2021-01-041-2/+2
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-040-0/+0
|\ \ | |/ | | | | | | * PHP-7.3: [ci skip] Unpdate NEWS
| * [ci skip] Unpdate NEWSStanislav Malyshev2021-01-041-0/+2
| |
* | Merge branch 'PHP-7.3' into PHP-7.4Stanislav Malyshev2021-01-017-15/+61
|\ \ | |/ | | | | | | * PHP-7.3: Fix #77423: parse_url() will deliver a wrong host to user
| * Merge branch 'PHP-7.2' into PHP-7.3Stanislav Malyshev2021-01-017-15/+61
| |\ | | | | | | | | | | | | * PHP-7.2: Fix #77423: parse_url() will deliver a wrong host to user
| | * Fix #77423: parse_url() will deliver a wrong host to userPHP-7.2Christoph M. Becker2021-01-017-14/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | To avoid that `parse_url()` returns an erroneous host, which would be valid for `FILTER_VALIDATE_URL`, we make sure that only userinfo which is valid according to RFC 3986 is treated as such. For consistency with the existing url parsing code, we use ctype functions, although that is not necessarily correct.
* | | Replace sort() function calls with ksort() in basic ksort testhaszi2020-12-271-27/+27
| | | | | | | | | | | | Closes GH-6541.
* | | Fix #80384: limit read buffer sizeAdam Seitz2020-12-234-2/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case of a stream with no filters, php_stream_fill_read_buffer only reads stream->chunk_size into the read buffer. If the stream has filters attached, it could unnecessarily buffer a large amount of data. With this change, php_stream_fill_read_buffer only proceeds until either the requested size or stream->chunk_size is available in the read buffer. Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de> Closes GH-6444.
* | | Fixed bug #80376 (last day of the month causes runway cpu usage)Derick Rethans2020-12-213-16889/+19647
| | |
* | | MySQLnd: Support cursors in store/get resultNikita Popov2020-12-185-92/+231
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes two related issues: 1. When a PS with cursor is used in store_result/get_result, perform a COM_FETCH with maximum number of rows rather than silently switching to an unbuffered result set (in the case of store_result) or erroring (in the case of get_result). In the future, we might want to make get_result unbuffered for PS with cursors, as using cursors with buffered result sets doesn't really make sense. Unlike store_result, get_result isn't very explicit about what kind of result set is desired. 2. If the client did not request a cursor, but the server reports that a cursor exists, ignore this and treat the PS as if it has no cursor (i.e. to not use COM_FETCH). It appears to be a server side bug that a cursor used inside an SP will be reported to the client, even though the client cannot use the cursor. Fixes bug #64638, bug #72862, bug #77935. Closes GH-6518.
* | | Fixed bug #67983Nikita Popov2020-12-163-22/+62
| | | | | | | | | | | | | | | We need to check the BIT case first, otherwise it will get skipped in INT_AND_FLOAT_NATIVE mode.
View Lorry Controller Status