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
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
Hi Ralph,
I'm aware of the ability to use a routing script to determine which files to
serve via a return false;.
My concern is that every framework / application etc is going to need one in
order to work with the built-in server (even if they all need the same
one!)..
So considering this
it does seem silly that the server would even try to serve those files
rather than check if they are of a certain header/mime before, but at least
with this method it does mean that you can fix your code to always bypass
this, and if your purposlly testing through the CLI-server anyway, changing
