4 ms·

There are benefits to keeping your routing in your app. Using different route sets based on environment variables, specifically migrating from one version of a

There are benefits to keeping your routing in your app. Using different route sets based on environment variables, specifically migrating from one version of an api to another is not possible or easy with a purely htaccess router. But I agree that in some cases the fastest you can do is an htaccess route.

benatkin 14y ago
> There are benefits to keeping your routing in your app. Using different route sets based on environment variables, specifically migrating from one version of an api to another is not possible or easy with a purely htaccess router. I'm not excited to correct you, because the way it it doesn't quite hold true involves dragons, but I thought I would in case people doubt the power of apache configuration (nginx is much the same way). It is possible, with included modules like the one below. There is also the ability to use custom modules, which are programmatic in nature and have access to Apache at a low level. Since it wasn't specified whether a shared host is being used, I think it's within the scope of the discussion. http://httpd.apache.org/docs/2.2/env.html http://httpd.apache.org/docs/2.2/env.html