Basic routing using REQUEST_URI

So for nginx it is not straightforward to setup PHP-FPM so that PATH_INFO is correctly populated. Lamb uses the following /index.php/some/other type routing, where /some/other should be the PATH_INFO. Instead I want to make setup for a variety of web-servers straightforward, so I've switched to the more robust REQUEST_URI. This simplifies nginx configuration and Caddy and the PHP built-in web-server are compatible.

REQUEST_URI contains everything after the domain name, including the query string, so that needs to be removed:

$request_uri = '/home';
if ( $_SERVER['REQUEST_URI'] !== '/' ) {
    $request_uri = strtok( $_SERVER['REQUEST_URI'], '?' );
}

We can see that for a request for the root of the site, REQUEST_URI returns / whereas PATH_INFO would be empty, so the code above takes that into account. We can then deduct a router action as follows:

$action = strtok( $request_uri, '/' );

Once the $action is known, it can be checked against an allowed list of actions:

switch ( $action ) {
    case 'edit':
        ...
        break;
    default:
        respond_404();
        break;

#php #lamb

March 21 at 12:41 pm

Related posts

  • January 31 at 11:57 am
  • January 2 at 9:59 am PHP-Activate 0.3.1
  • December 15 at 9:47 am PHP-Activate 0.3.0
  • October 5 at 8:59 am PHP-Activate 0.2.0
  • March 21 at 2:28 pm
  • March 21 at 12:41 pm Basic routing using REQUEST_URI
  • January 3 at 2:07 pm
  • December 6 at 2:28 pm Lamb image test
  • July 28 at 11:43 am Lamb 0.3.0
  • March 24 at 9:46 am Lamb 0.2
  • March 16 at 4:49 pm
  • March 15 at 12:42 pm