|
Revision tags: php-8.1.7RC1, php-8.1.4RC1, php-8.1.3, php-8.1.2RC1, php-8.1.0, php-7.3.33, php-7.3.32, php-7.3.31, php-7.3.30 |
|
| #
cd0cd3d3 |
| 01-Aug-2021 |
Kamil Tekiela |
Fix typos (#7327) |
|
Revision tags: php-7.3.29 |
|
| #
aff36587 |
| 29-Jun-2021 |
Patrick Allaert |
Fixed some spaces used instead of tabs |
| #
aca6aefd |
| 14-May-2021 |
George Peter Banyard |
Remove 'register' type qualifier (#6980)
The compiler should be smart enough to optimize this on its own |
| #
01b3fc03 |
| 06-May-2021 |
KsaR |
Update http->https in license (#6945)
1. Update: http://www.php.net/license/3_01.txt to https, as there is anyway server header "Location:" to https.
2. Update few license 3.0 to 3.01 as
Update http->https in license (#6945)
1. Update: http://www.php.net/license/3_01.txt to https, as there is anyway server header "Location:" to https.
2. Update few license 3.0 to 3.01 as 3.0 states "php 5.1.1, 4.1.1, and earlier".
3. In some license comments is "at through the world-wide-web" while most is without "at", so deleted.
4. fixed indentation in some files before |
show more ...
|
|
Revision tags: php-7.3.28, php-7.3.27 |
|
| #
23961ef3 |
| 27-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-8.0'
* PHP-8.0:
Rm unneeded function
|
| #
e9b8b085 |
| 27-Jan-2021 |
Stanislav Malyshev |
Rm unneeded function |
| #
7eff4057 |
| 27-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-8.0'
* PHP-8.0:
Alternative fix for bug 77423
|
| #
effa287b |
| 27-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-7.4' into PHP-8.0
* PHP-7.4:
Alternative fix for bug 77423
|
| #
fbf8c758 |
| 27-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-7.3' into PHP-7.4
* PHP-7.3:
Alternative fix for bug 77423
|
| #
4a89e726 |
| 19-Jan-2021 |
Christoph M. Becker |
Alternative fix for bug 77423
That bug report originally was about `parse_url()` misbehaving, but the
security aspect was actually only regarding `FILTER_VALIDATE_URL`.
Since the cha
Alternative fix for bug 77423
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>
show more ...
|
| #
3e01f5af |
| 15-Jan-2021 |
Nikita Popov |
Replace zend_bool uses with bool
We're starting to see a mix between uses of zend_bool and bool.
Replace all usages with the standard bool type everywhere.
Of course, zend_bool
Replace zend_bool uses with bool
We're starting to see a mix between uses of zend_bool and bool.
Replace all usages with the standard bool type everywhere.
Of course, zend_bool is retained as an alias.
show more ...
|
| #
ced4c0bf |
| 04-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-7.4' into PHP-8.0
* PHP-7.4:
[ci skip] Update NEWS
[ci skip] Fix order
[ci skip] Unpdate NEWS
Fix #77423: parse_url() will deliver a wrong host to u
Merge branch 'PHP-7.4' into PHP-8.0
* PHP-7.4:
[ci skip] Update NEWS
[ci skip] Fix order
[ci skip] Unpdate NEWS
Fix #77423: parse_url() will deliver a wrong host to user
show more ...
|
|
Revision tags: php-7.3.26, php-7.3.26RC1, php-7.3.25, php-7.3.25RC1, php-7.3.24, php-7.3.24RC1, php-7.3.23, php-7.3.23RC1, php-7.3.22, php-7.3.22RC1, php-7.3.21, php-7.3.21RC1, php-7.3.20, php-7.3.20RC1, php-7.3.19, php-7.4.7RC1, php-7.3.19RC1 |
|
| #
5174de7c |
| 13-May-2020 |
Christoph M. Becker |
Fix #77423: parse_url() will deliver a wrong host to user
To avoid that `parse_url()` returns an erroneous host, which would be
valid for `FILTER_VALIDATE_URL`, we make sure that only us
Fix #77423: parse_url() will deliver a wrong host to user
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.
show more ...
|
| #
b132da7f |
| 13-May-2020 |
Christoph M. Becker |
Fix #77423: parse_url() will deliver a wrong host to user
To avoid that `parse_url()` returns an erroneous host, which would be
valid for `FILTER_VALIDATE_URL`, we make sure that only us
Fix #77423: parse_url() will deliver a wrong host to user
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.
show more ...
|
| #
434c2b1b |
| 02-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-7.3' into PHP-7.4
* PHP-7.3:
Fix #77423: parse_url() will deliver a wrong host to user
|
| #
128fca40 |
| 02-Jan-2021 |
Stanislav Malyshev |
Merge branch 'PHP-7.2' into PHP-7.3
* PHP-7.2:
Fix #77423: parse_url() will deliver a wrong host to user
|
| #
2d3d7241 |
| 13-May-2020 |
Christoph M. Becker |
Fix #77423: parse_url() will deliver a wrong host to user
To avoid that `parse_url()` returns an erroneous host, which would be
valid for `FILTER_VALIDATE_URL`, we make sure that only us
Fix #77423: parse_url() will deliver a wrong host to user
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.
show more ...
|
| #
b8f2531f |
| 04-Nov-2020 |
Christoph M. Becker |
Merge branch 'PHP-7.4' into PHP-8.0
* PHP-7.4:
Fix #80266: parse_url silently drops port number 0
|
| #
00e41a10 |
| 04-Nov-2020 |
Christoph M. Becker |
Merge branch 'PHP-7.3' into PHP-7.4
* PHP-7.3:
Fix #80266: parse_url silently drops port number 0
|
| #
2cab085b |
| 04-Nov-2020 |
Christoph M. Becker |
Fix #80266: parse_url silently drops port number 0
As of commit 81b2f3e[1], `parse_url()` accepts URLs with a zero port,
but does not report that port, what is wrong in hindsight.
Fix #80266: parse_url silently drops port number 0
As of commit 81b2f3e[1], `parse_url()` accepts URLs with a zero port,
but does not report that port, what is wrong in hindsight.
Since the port number is stored as `unsigned short` there is no way to
distinguish between port zero and no port. For BC reasons, we thus
introduce `parse_url_ex2()` which accepts an output parameter that
allows that distinction, and use the new function to fix the behavior.
The introduction of `parse_url_ex2()` has been suggested by Nikita.
[1] <http://git.php.net/?p=php-src.git;a=commit;h=81b2f3e5d9fcdffd87a4fcd12bd8c708a97091e1>
Closes GH-6399.
show more ...
|
| #
76e4bf30 |
| 24-Oct-2020 |
Máté Kocsis |
Parameter type and name fixes in ext/standard
Closes GH-6382 |
| #
c0f8cc19 |
| 20-Sep-2020 |
Christoph M. Becker |
Merge branch 'PHP-7.4' into master
* PHP-7.4:
Fix #80114: parse_url does not accept URLs with port 0
|
| #
105132bd |
| 20-Sep-2020 |
Christoph M. Becker |
Merge branch 'PHP-7.3' into PHP-7.4
* PHP-7.3:
Fix #80114: parse_url does not accept URLs with port 0
|
| #
81b2f3e5 |
| 20-Sep-2020 |
Christoph M. Becker |
Fix #80114: parse_url does not accept URLs with port 0
URIs with a 0 port are generally valid, so `parse_url()` should
recognize such URIs, but still report the port as missing.
Fix #80114: parse_url does not accept URLs with port 0
URIs with a 0 port are generally valid, so `parse_url()` should
recognize such URIs, but still report the port as missing.
Co-authored-by: twosee <twose@qq.com>
Closes GH-6152.
show more ...
|
| #
4a2ae841 |
| 07-Sep-2020 |
Dmitry Stogov |
Add "const". Move constant strings to read-only memory. |
