[Tickets #6264] Re: Global "pretty urls" config setting

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=6264
-----------------------------------------------------------------------
 Ticket             | 6264
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Global "pretty urls" config setting
 Queue              | Horde Base
 Version            | HEAD
 Type               | Enhancement
-State              | Resolved
+State              | Feedback
 Priority           | 2. Medium
 Milestone          | Horde 3.2
 Patch              | 
 Owners             | Chuck Hagenbuch
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-02-26 01:16) wrote:

> 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.