Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53870
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain smashlabs.com from 67.15.58.61 cause and error)
Message-ID: <4E1B0579.8000307@smashlabs.com>
Date: Mon, 11 Jul 2011 09:15:21 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAGSj+Qu=x7r=ekdGoX85C-Sk7gQidXXTA7akEHpsjZgGs0q6-w@mail.gmail.com>
In-Reply-To: <CAGSj+Qu=x7r=ekdGoX85C-Sk7gQidXXTA7akEHpsjZgGs0q6-w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Built-in web server routing script and static assets
From: ralph@smashlabs.com (Ralph Schindler)

Hey Kiall,

An optional argument to the built in web server can be a php based 
router.  If the router returns false, it will attempt to return the 
resource as-it-is on disk.

Your command line looks like this:

php -S localhost:8000 -t ./path/to/docroot routing.php

routing.php can be one of two things- either a drop in replacement for 
.htaccess or your sites index.php.

My routing.php looks like this:

<?php

   // OR if (preg_match('/\.(?:png|jpg|jpeg|gif)$/', 
$_SERVER["REQUEST_URI"]))
   if (file_exists(__DIR__ . '/' . $_SERVER['REQUEST_URI'])) {
     return false; // serve the requested resource as-is.
   } else {
     include_once 'index.php';
   }


If you choose to put your index.php in as the router, then your 
index.php should be cli-server aware:

   <?php

   if (php_sapi_name() == 'cli-server') {
     /* route static assets and return false */
   }

   /* go on with normal index.php operations */


I like the former approach as the routing.php can go inside your version 
control ignore list and won't get checked in as part of the project.

To me, that is as many lines of Apache rewrite that one would have had 
and it is as feature complete as Apache rewrite.

-ralph


On 7/11/11 6:46 AM, Kiall Mac Innes wrote:
> Hiya,
>
> I've been playing with the built-in server, and have some concerns over how
> static assets are handled.
>
> Currently, to run an application on the built-in server, we essentially need
> to list out all the static assets that should be served directly from disk.
> This is the opposite of what I believe the most common web server
> configurations use.
>
> I believe the built-in server should mimic typical configurations, rather
> than requiring applications to write code solely for PHP's web server.
>
> Have I just missed something? or if not, what do people think of how static
> files are handled currently?
>
> A typical Apache config extract (IMHO):
>
> # Turn on URL rewriting
> RewriteEngine On
> RewriteBase /
>
> # Allow any files or directories that exist to be displayed directly
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
>
> # Rewrite all other URLs to index.php/URL
> RewriteRule .* index.php/$0 [PT]
>
> Apologies is this has been brought up before, I've not seen any discussion
> of this topic so far.
>
> Thanks,
> Kiall
>