Removed UPGRADING note

Conflicts:
UPGRADING

Implemented FR #65917 (getallheaders() is not supported by the built-in...)

- Implemented apache_request_headers() and getallheaders() alias in CLI server
- Implemented apache_response_h

Implemented FR #65917 (getallheaders() is not supported by the built-in...)

- Implemented apache_request_headers() and getallheaders() alias in CLI server
- Implemented apache_response_headers() in CLI server using FastCGI code

Conflicts:
NEWS
UPGRADING

show more ...

Fixed case part of bug #64874 ("json_decode handles whitespace and case-sensitivity incorrectly")

Update NEWS and remove the unnecessary UPGRADING note.

bump version, empty NEWS, UPGRADING and UPGRADING.INTERNALS

NEWS + UPGRADING

Fix English here

Add crypt() change in UPGRADING

ldap_escape() notes

Retruning SUCCESS/FAILURE instead of int

UPGRADING and NEWS

Thanks Daniel, I didn't think long enough

openssl NEWS,UPGRADING

add NEWS and UPGRADING about gost-crypto

fix bug #55285 XMLReader::getAttribute/No/Ns methods inconsistency

Implement variadic function syntax

As per RFC: https://wiki.php.net/rfc/variadics

Fix typo: HTTP_ROW_POST_DATA → HTTP_RAW_POST_DATA.

Fixes bug #65745 (Typo in commit 4a3936ef4abdeb72c7d323fe4b6a65e1ae0ef181).

NEWS/UPGRADING{,.INTERNALS} notes about temp POST stream

Request non-keep-alive connections by default in HTTP 1.1 requests.

As noted in FR #65634, at present we don't send a Connection request header
when the protocol version is set to 1.1, w

Request non-keep-alive connections by default in HTTP 1.1 requests.

As noted in FR #65634, at present we don't send a Connection request header
when the protocol version is set to 1.1, which means that RFC-compliant Web
servers should respond with keep-alive connections. Since there's no way of
reusing the HTTP connection at present, this simply means that PHP will appear
to hang until the remote server hits its connection timeout, which may be quite
some time.

This commit sends a "Connection: close" header by default when HTTP 1.1 (or
later) is requested by the user via the context options. It can be overridden
by specifying a Connection header in the context options. It isn't possible to
disable sending of the Connection header, but given "Connection: keep-alive" is
the same as the default HTTP 1.1 behaviour, I don't see this as a significant
issue — users who want to opt in for that still can.

As a note, although I've removed an efree(protocol_version), this doesn't
result in a memory leak: protocol_version is freed in the out: block at the end
of the function anyway, and there are no returns between the removed efree()
and the later call. Yes, I ran the tests with valgrind to check that. ☺

Implements FR #65634 (HTTP wrapper is very slow with protocol_version 1.1).

show more ...

Update NEWS/UPGRADING with info about incompat ctx

Expose fputcsv's escape_char to userland

Allows users to assert that something other than the backslash
should be considered an escape char; also follows the RFC 4180
recommendation

Expose fputcsv's escape_char to userland

Allows users to assert that something other than the backslash
should be considered an escape char; also follows the RFC 4180
recommendation that fields containing a " be enclosed.

show more ...

add upgrading notes about bison and 2Guploads

add news about session fix

add news about session fix

Update UPGRADING and make typo fixes to OCI8 package.xml