Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100107
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
Date: Sat, 29 Jul 2017 17:52:19 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <67.EC.40376.A469C795@pb1.pair.com>
References: <CAESVnVpF53Nn=K-CbVh8NSEqzebpdzZ7WgGsq91TWfo47GbEJw@mail.gmail.com> <72B777E0-9E71-4D63-A9D0-20FD62F1A187@gmail.com> <67.EC.40376.A469C795@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Andrea Faulds <ajf@ajf.me>
Message-ID: <18CBF3A9-DD0B-4B66-A2EF-046BE46FC7AF@gmail.com>
Subject: Re: [PHP-DEV] Changes to SuperGlobals for PHP 8 (was: something about session_start...)
From: rowan.collins@gmail.com (Rowan Collins)

On 29 July 2017 15:05:57 BST, Andrea Faulds <ajf@ajf=2Eme> wrote:
>Hi Rowan,
>
>Rowan Collins wrote:
>> On a slight tangent, I consider $_SERVER to be a broken pile of
>"we'll just shove this in here and hope for the best", and I will
>oppose any attempt to convert it into an object which doesn't
>reorganize its keys to be sane, documented, and as cross-platform as
>the SAPI layer can make it=2E :P
>
>$_SERVER makes sense to me, its content is what the CGI environment=20
>variables would be (or are, if you're actually using CGI in 2017)=2E
>Those=20
>are standardised=2E

But what does a standardised CGI variable list have to do with anything wh=
en you're running under an Apache module, or one of our two fast-cgi SAPIs,=
 let alone if we ever want event-based or asynchronous SAPIs to be a thing?=
=20

If you want to know the URL the user requested, you have to know about the=
 subtle differences between half a dozen different variables which will be =
populated differently, or not at all, depending on your configuration=2E So=
me of this is inevitable because there are too many different ways of achie=
ving the same thing, but at least some of it is known by the SAPI, which no=
netheless blindly populates $_SERVER with whatever the hosting server provi=
ded=2E

And talking of name mangling, CGI mangles the request HTTP headers in its =
own quirky way, when they should just be a structure of their own separate =
from this generic environment=2E That particular quirk can even cause secur=
ity problems, IIRC=2E

Regards,

--=20
Rowan Collins
[IMSoP]