Fri, 10 Apr 2026 09:21:02 +0000 https://bugs.horde.org/ticket/6264 Global "pretty urls" config setting I'd like to add a Horde-level "pretty urls" config setting - something like $conf['urls'] with options for regular query_string, mod_rewrite, path_info, and forcetype style URLs. That way apps like Ansel and Whups (Horde 3.2+ apps) don't need their own settings, and would have a way of knowing if they should generate pretty URLs or GET URLs. If there are no objections I'd like to get this into Horde 3.2. Fri, 15 Feb 2008 06:31:01 +0000 https://bugs.horde.org/ticket/6264#t42377 Added with No (false) and 'mod_rewrite' options for now. Michael R., what sort of rules do you have for lighttpd? We should add those somewhere too. Mon, 25 Feb 2008 03:59:34 +0000 https://bugs.horde.org/ticket/6264#t42938 > Added with No (false) and 'mod_rewrite' options for now. Michael R., > what sort of rules do you have for lighttpd? Basically, code written to work with mod_rewrite will work with lighttpd's url.rewrite module, but the rewrite rules themselves are written differently. We can maybe include snippet of the rewrite rules somewhere in the docs but it's not as easy to have them be dropped in like they are with apache's .htaccess files. Forcetype style urls aren't really supported per se in lighttpd but they can be simulated with rewrite rules. I haven't really tried it in depth, but using PATH_INFO would probably work OK with lighttpd. I'm thinking the easiest thing to do would be to either have a 'lighttpd' configuration choice, that is basically an alias of mod_rewrite, or just a note somewhere to use mod_rewrite if you are using (and have configured) lighttpd rewrite rules... Mon, 25 Feb 2008 15:54:47 +0000 https://bugs.horde.org/ticket/6264#t42959 > Basically, code written to work with mod_rewrite will work with > lighttpd's url.rewrite module, but the rewrite rules themselves are > written differently. We can maybe include snippet of the rewrite > rules somewhere in the docs but it's not as easy to have them be > dropped in like they are with apache's .htaccess files. [snip] > I'm thinking the easiest thing to do would be to either have a > 'lighttpd' configuration choice, that is basically an alias of > mod_rewrite, or just a note somewhere to use mod_rewrite if you are > using (and have configured) lighttpd rewrite rules... Okay, so how about we have 'none' (as now), meaning GET urls, 'rewrite', meaning mod_rewrite or lighttpd rules or whatever, and 'base_url' (better names?) meaning PATH_INFO or ForceType or Horde_Routes - anything with a single script as the base. With this last one, we'd include an additional option to actually set the base_url to use. We could make this portable across apps by having a single routing file in Horde that dispatched to apps that use pretty URLs. Would be a bit of a hack on top of the existing stuff, but easier to deal with than the current mish-mash of rewrite rules. Tue, 26 Feb 2008 06:16:51 +0000 https://bugs.horde.org/ticket/6264#t43077 Sounds good to me. Tue, 26 Feb 2008 10:27:38 +0000 https://bugs.horde.org/ticket/6264#t43082 Sounds good to me as well...assuming the apps being released for Horde 3.2 can still code for it the 'old' way. Tue, 26 Feb 2008 15:29:53 +0000 https://bugs.horde.org/ticket/6264#t43107 > assuming the apps being released for Horde 3.2 can still code for it the 'old' way. Not sure what you mean by this? Tue, 26 Feb 2008 16:32:42 +0000 https://bugs.horde.org/ticket/6264#t43112 Sorry. I basically mean without the Horde Routes stuff, like the way Chora, for example, currently handles it... Tue, 26 Feb 2008 16:38:50 +0000 https://bugs.horde.org/ticket/6264#t43113 Right, Routes won't be a requirement, but I was thinking of support in Horde 3.2 for generalizing PATH_INFO and ForceType style URLs. Tue, 26 Feb 2008 18:07:58 +0000 https://bugs.horde.org/ticket/6264#t43117 Okay, the config setting is tweaked and should be good now. PATH_INFO and ForceType are still going to be tricky perhaps. Tue, 26 Feb 2008 18:54:35 +0000 https://bugs.horde.org/ticket/6264#t43125