Home/ Questions/Q 3320326
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:55:48+00:00

As almost every programmer, I’m writing my own PHP framework for educational purposes. And

  • 0

As almost every programmer, I’m writing my own PHP framework for educational purposes. And now I’m looking at the problem with parsing URLs for MVC routing.

Framework will use friendly URLs everywhere. But the question is how to parse them in front controller. For example the link /foo/bar/aaa/bbb may mean “Call the controller’s foo action bar and pass parameter aaa with value bbb. But in case someone installs a framework into the subdirectory of the domain root, the directory part should be stripped before determining controller name and action name. And I’m looking for a way to do it safely.

Also I would like to support a fallback case if URL rewriting is not supported on the server.

On different systems different sets of $_SERVER variables are defined. For example, on my local machine from the set of PATH_INFO, REQUEST_URI, REQUEST_URL, ORIG_REQUEST_URI, SCRIPT_NAME, PHP_SELF only REQUEST_URI, SCRIPT_NAME and PHP_SELF are defined. I wonder, if I can rely on them.

Mature frameworks like Symfony or ZF have some compicated algorithms of parsing URLs (at least it seemed to be so). So, I can’t just take a part from there for mine.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m currently doing the same research. But everything I see is so complicated that I’ll most probably continue using mod_rewrite anyway. After all you end up with the same thing rather you use SEF with PHP or mod_rewrite with apache. Anyway I’ll be monitoring this topic.. it’s interesting 🙂
    Hope the php gurus around here have some more info about this 🙂

    Edit:
    It really depends on what you want to do. For my needs I hardcoded most of the pages so they looked SEF. But something like the example below should work as well.

    RewriteEngine on
RewriteRule ^/posts/([A-Za-z0-9_\-]+)/([A-Za-z0-9_\-]+)\.html$ posts.php?$1=$2 [NC]

    With this example above:

    http://localhost/posts/view/23 
http://localhost/posts/delete/23

    is equal to:

    http://localhost/posts.php?view=23
http://localhost/posts.php?delete=23

    It really depends on what exactly you’re doing 🙂
    The example above should be working but I haven’t tested them.

    • 0