Re: Re: Access-Control-Allow-Origin header in CLI server

From: Date: Sat, 06 Jul 2013 17:07:19 +0000
Subject: Re: Re: Access-Control-Allow-Origin header in CLI server
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-68073@lists.php.net to get a copy of this message
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

« previous php.internals (#68073) next »