delta/php-git.git/sapi/cli/tests/bug66830.phpt, branch php-7.4.1 git.php.net: repository/php-src.git Sync leading and final newlines in *.phpt sections 2018-10-15T02:33:09+00:00 Peter Kokot peterkokot@gmail.com 2018-10-15T02:33:09+00:00 d679f02295ea079338f029b7f5f4cb65b37f190c 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
Added mandatory Date: header to built-in webserver 2016-06-02T10:27:48+00:00 SeeSchloss see@seos.fr 2016-01-21T17:20:24+00:00 f33c7b3e41bda272de83bcc4959b3e0b968e3124 






Merge branch 'PHP-5.5' into PHP-5.6
2014-07-07T20:45:01+00:00

Adam Harvey
aharvey@php.net

2014-07-07T20:45:01+00:00

70e9d3e2f9d7bc0b48811f01c084f82524af604c

* PHP-5.5:
  Fixed bug #66830 (Empty header causes PHP built-in web server to hang).





* PHP-5.5:
  Fixed bug #66830 (Empty header causes PHP built-in web server to hang).







Fixed bug #66830 (Empty header causes PHP built-in web server to hang).
2014-07-07T20:36:06+00:00

Adam Harvey
aharvey@php.net

2014-07-07T20:36:06+00:00

604de67b7d0b8c6db76002011e3b55dd9c7aeec8

We had an infinite loop in sapi_cli_server_send_headers(): while iterating over
the linked list of headers, when an empty header was hit, continue would go to
the next iteration of the loop without updating h to be the next value in the
linked list. Updating it to always increment regardless of whether the header
is actually valid or not fixes the issue.





We had an infinite loop in sapi_cli_server_send_headers(): while iterating over
the linked list of headers, when an empty header was hit, continue would go to
the next iteration of the loop without updating h to be the next value in the
linked list. Updating it to always increment regardless of whether the header
is actually valid or not fixes the issue.