Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAA=k7mWP_Nn_wJp9VdaQ4vxCCZQmbBaFsHyzOPVjkRK3LRNbNQ@mail.gmail.com>
References: <CAH8Mpnmn8MMEN-WLRLSvgppe5RzPjK6NwyXhyuh7FDKU4fxfuA@mail.gmail.com>
	<CAN=kQJctJfkZ-DtJFH1cOouWO9EQG+ja_Gqm6diX62v9PD2DjQ@mail.gmail.com>
	<CAA=k7mWP_Nn_wJp9VdaQ4vxCCZQmbBaFsHyzOPVjkRK3LRNbNQ@mail.gmail.com>
Date: Sat, 6 Jul 2013 12:07:19 -0500
Message-ID: <CAN=kQJeDH-BomNqTAadVUjO2TuSHFKEvSxPj3qkU3vrKVN=fvw@mail.gmail.com>
To: Mario Brandt <jblond@gmail.com>
Cc: Daniel Lowrey <rdlowrey@gmail.com>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server
From: leverton@gmail.com (Matthew Leverton)

On Sat, Jul 6, 2013 at 7:59 AM, Mario Brandt <jblond@gmail.com> wrote:
> You can use the router script to add that header of your desire into
> every request.
>
That's what I currently do. And I agree that if somebody wants to
deviate from the reasonable set of defaults that PHP provides, then he
must set them in a router script. I don't think the CLI server should
be a configurable web server.

But IMO, this is no different from PHP maintaining and delivering a
small set of Content-type headers. Of course you could take the same
hardline approach and tell the developer to set all of the content
headers himself because you're worried that somebody might use PNG as
a data file that holds ping pong scores. But neither the existence of
this nor the content-type have any reasonable side effects.

I'm just throwing this out here; I've got nothing more to say and am
fine with the powers-to-be doing whatever they feel appropriate.

--
Matthew Leverton