Rewrite handling [was Things I'd like moved ...]

I think I might have found the holy grail of all things rewrite-help related:

http://forum.modrewrite.com/index.php

Reading over this again, I realized that I did a piss poor job of explaining what I was getting at

Jason, you’re 100% right -- we still need mod_rewrite, or some Apache directive to send every request to a single resource no matter what. From there, we do an internal lookup if that resource exists in the DB and send back a 200 or a 404 status and render the proper page (or an error). It’s not horribly different from he way do it now, except that it’ll be a little smoother with an internal dispatcher rather than everything being redirected to index.php (which is how we manage it now).

Hopefully that makes more sense

Quote from: rthrash at Nov 08, 2005, 11:25 AM

Quote from: vbrilon at Nov 08, 2005, 11:20 AM

What I am suggesting is creating a mechanism that’ll accept *any* request (this is easy to do with Apache and IIS) and then process that internally based on the virtual document that should be returned (or not -- in the case of errors).

If all requests are being passed along as a parameter, how will you ever get your 404s to register in your apache logs?

Because the processor can then view the request, see if a virtual document with that path exists or a real physical document with that path exists, and if the answer is no, then return a 404 to Apache. We’re already doing everything but that last step anyway.