Re: [PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server

2013-07-18 Thread Yasuo Ohgaki
Hi Matthew, 2013/7/7 Matthew Leverton lever...@gmail.com On Sat, Jul 6, 2013 at 7:59 AM, Mario Brandt jbl...@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

Re: [PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server

2013-07-06 Thread Mario Brandt
You can use the router script to add that header of your desire into every request. Cheers Mario On 6 July 2013 01:34, Matthew Leverton lever...@gmail.com wrote: On Fri, Jul 5, 2013 at 5:48 PM, Daniel Lowrey rdlow...@gmail.com wrote: This is not the sort of thing that belongs in an HTTP

Re: [PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server

2013-07-06 Thread Matthew Leverton
On Sat, Jul 6, 2013 at 7:59 AM, Mario Brandt jbl...@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

[PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server

2013-07-05 Thread Daniel Lowrey
This is not the sort of thing that belongs in an HTTP server by default. It's a one-off header that some users may elect to send but the vast majority will not. If you need to simulate the feature of an third-party server mod/plugin you should manually make a `header('Access-Control-Allow-Origin:

Re: [PHP-DEV] Re: Access-Control-Allow-Origin header in CLI server

2013-07-05 Thread Matthew Leverton
On Fri, Jul 5, 2013 at 5:48 PM, Daniel Lowrey rdlow...@gmail.com wrote: This is not the sort of thing that belongs in an HTTP server by default. It's a one-off header that some users may elect to send but the vast majority will not. Of course I agree if you were speaking about a production web