I love this module, it really helps get rid of all those stupid URLs that people (and search engines, I guess) somehow find out about when there's a proper URL for the page. I also understand that this module needs database access, and so has a hard time working with aggressive caching.

However, it would be cool to have a way to run the module "on demand", i.e., only for URLs that start with a pattern like "/node/". This could even be done outside of Drupal, using rewrite rule. Since accesses to /node/ URLs are not very common, this would not cause a big performance hit. As it is, globalredirect is the only module that is keeping me from using aggressive caching, and I would really like to switch over to that.

Comments

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Status: Active » Closed (works as designed)

Although possible to run this module in aggressive caching mode, I am pretty sure it wouldn't work. As I understand it - aggressive caching only works so well because it doesn't load a hell of a lot of Drupal code up (its almost literally pulling the page out of cache and printing it).

I might investigate the impact of moving the code from hook_init to hook_menu... However I still believe this could cause issues and possibly even harm the performance of the site.