summaryrefslogtreecommitdiff
path: root/ext/session
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'PHP-7.2' into PHP-7.3Christoph M. Becker2019-05-212-5/+5
|\ | | | | | | | | * PHP-7.2: use {TMP} placeholder in phpt tests
| * use {TMP} placeholder in phpt testsHolly Li (WIPRO LIMITED)2019-05-212-5/+5
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Christoph M. Becker2019-04-171-1/+1
|\ \ | |/ | | | | | | * PHP-7.2: Fix #77911: Wrong warning for session.sid_bits_per_character
| * Fix #77911: Wrong warning for session.sid_bits_per_characterChristoph M. Becker2019-04-171-1/+1
| |
| * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1598-107/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * Trim trailing whitespace in *.phptPeter Kokot2018-10-14129-301/+301
| |
* | Fix session tests that fail if error_log is setRasmus Lerdorf2018-10-313-0/+3
| |
* | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1596-105/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Trim trailing whitespace in *.phptPeter Kokot2018-10-14128-299/+299
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Peter Kokot2018-10-148-8/+0
|\ \ | |/ | | | | | | * PHP-7.2: Fix failing ext/session/tests due to final newlines
| * Merge branch 'PHP-7.1' into PHP-7.2Peter Kokot2018-10-148-8/+0
| |\ | | | | | | | | | | | | * PHP-7.1: Fix failing ext/session/tests due to final newlines
| | * Fix failing ext/session/tests due to final newlinesPeter Kokot2018-10-148-8/+0
| | |
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. 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
| | * Trim trailing whitespace in source code filesPeter Kokot2018-10-135-6/+6
| | |
| | * Convert CRLF line endings to LFPeter Kokot2018-10-132-99/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
| * | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. 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
| * | Trim trailing whitespace in source code filesPeter Kokot2018-10-134-5/+5
| | |
| * | Convert CRLF line endings to LFPeter Kokot2018-10-131-57/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
* | | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. 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
* | | Trim trailing whitespace in source code filesPeter Kokot2018-10-131-1/+1
| | |
* | | Convert CRLF line endings to LFPeter Kokot2018-10-131-57/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
* | | Micro optimization & fixed invalid key handlingXinchen Hui2018-08-171-1/+3
| | |
* | | Fix #76688: Disallow excessive parameters after options arrayPedro Magalhães2018-08-122-0/+18
| | |
* | | Support for samesite cookies with array syntaxPedro Magalhães2018-07-316-45/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | | Allows using an alternative array argument with support for the samesite option on the following functions: setcookie setrawcookie session_set_cookie_params
* | | implement same site cookie see https://bugs.php.net/bug.php?id=72230 see ↵Frederik Bosch2018-07-317-16/+117
| | | | | | | | | | | | https://tools.ietf.org/html/draft-west-first-party-cookies-07 see https://scotthelme.co.uk/csrf-is-dead/
* | | Fix typos in code commentsPeter Kokot2018-07-251-1/+1
| | |
* | | Remove unused Git attributes identPeter Kokot2018-07-2510-20/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The $Id$ keywords were used in Subversion where they can be substituted with filename, last revision number change, last changed date, and last user who changed it. In Git this functionality is different and can be done with Git attribute ident. These need to be defined manually for each file in the .gitattributes file and are afterwards replaced with 40-character hexadecimal blob object name which is based only on the particular file contents. This patch simplifies handling of $Id$ keywords by removing them since they are not used anymore.
* | | Uze ZVAL_COPY_DEREF() instead of ZVAL_DEREF() and ZVAL_COPY()Dmitry Stogov2018-07-091-2/+1
| | |
* | | Use zval_ptr_dtor() imstead of zval_dtor()Dmitry Stogov2018-07-051-2/+2
| | |
* | | Replace legacy zval_dtor() by zval_ptr_dtor_nogc() or even more specialized ↵Dmitry Stogov2018-07-041-2/+2
| | | | | | | | | | | | | | | | | | | | | destructors. zval_dtor() doesn't make a lot of sense in PHP-7.* and it's used incorrectly in some places. Its occurances should be replaced by zval_ptr_dtor() or zval_ptr_dtor_nogc(), or even more specialized destructors.
* | | se zval_ptr_dtor_str() instead of zend_string_release_ex(Z_STR(*), 0)Dmitry Stogov2018-07-041-2/+2
| | |
* | | Use zend_string_release_ex() instread of zend_string_release() in places, ↵Dmitry Stogov2018-05-283-53/+53
| | | | | | | | | | | | where we sure about string persistence.
* | | Merge branch 'PHP-7.2'Anatol Belski2018-05-071-7/+8
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Update _bits_per_char to use with new PHP 7.1. or greater
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-05-071-7/+8
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Update _bits_per_char to use with new PHP 7.1. or greater
| | * Update _bits_per_char to use with new PHP 7.1. or greaterRicardo F2018-05-071-7/+8
| | | | | | | | | | | | | | | | | | Fix typo Remove references to PHP lower than 7.1
| | * year++Xinchen Hui2018-01-029-9/+9
| | |
* | | Merge branch 'PHP-7.2'Christoph M. Becker2018-04-121-0/+23
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fixed #74892 - Fixed URL rewriting for urls started with #
| * | Fixed #74892 - Fixed URL rewriting for urls started with #Andrew Nester2018-04-121-0/+23
| | | | | | | | | | | | | | | | | | | | | (cherry picked from commit 6c32d271d238a18cfc19d98877cdead1ab38f417) This should have already been merged via 9cd82df0bbb1f9a1407ffb749292576be1b91c07, but that merge went wrong.
* | | Remove duplicated testsGabriel Caruso2018-02-222-41/+0
| | |
* | | remove support for string|unicode in testsGabriel Caruso2018-02-2213-78/+78
| | |
* | | Use EXPECT instead of EXPECTF when possibleGabriel Caruso2018-02-2061-61/+61
| | | | | | | | | | | | EXPECTF logic in run-tests.php is considerable, so let's avoid it.
* | | Remove empty sections in testsGabriel Caruso2018-02-142-3/+2
| | |
* | | Remove trailing whitespace in inc filesGabriel Caruso2018-02-101-1/+1
| | |
* | | Fix some misspellingsGabriel Caruso2018-02-061-1/+1
| | |
* | | Use bool instead of boolean while throwing a type errorGabriel Caruso2018-02-043-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PHP requires boolean typehints to be written "bool" and disallows "boolean" as an alias. This changes the error messages to match the actual type name and avoids confusing messages like "must be of type boolean, boolean given". This a followup to ce1d69a1f6dcf15d43029301059c25e5bc09a577, which implements the same change for integer->int.
* | | Use int instead of integer in type errorsGabriel Caruso2018-02-041-4/+4
| | | | | | | | | | | | | | | | | | | | | PHP requires integer typehints to be written "int" and does not allow "integer" as an alias. This changes type error messages to match the actual type name and avoids confusing messages like "must be of the type integer, integer given".
* | | Remove superfluous SKIPIF sections in more testsGabriel Caruso2018-02-041-1/+0
| | |
* | | Remove checks for unicode.semantics ini optionNikita Popov2018-02-031-7/+0
| | |
* | | Use %d when expecting line number in testsGabriel Caruso2018-02-021-1/+1
| | |
* | | Merge branch 'PHP-7.2'Nikita Popov2018-01-241-1/+6
|\ \ \ | |/ /
View Lorry Controller Status