[cvs] [Wiki] changed: Doc/Admin/Config/Horde

[Jan Schneider]

jan  Fri, 14 Aug 2009 09:33:04 -0400

Modified page: http://wiki.horde.org/Doc/Admin/Config/Horde
New Revision:  1.2
Change log:  Fix markup

@@ -21,5 +21,5 @@
  The second is the prettiest because it looks like a static file, is  
short and recognizable. But it only works on web servers that support  
URL rewriting. Since there is no script file in that path at all,the  
rewrite rules have to map this URL internally to an existing script.  
In this example it would map foo/arg/value to  
foo/script.php?arg=value, without the user noticing anything about that.

  On the PHP side, the first one has to be supported anyway, the  
second one (path info) has to handled separately. That's why it  
doesn't work in all scripts, but only in certain. The third one is  
never seen by PHP, since the webserver is internally calling the  
rewritten URL instead.

-In horde/rpc.php for example we support all 3 versions. If they  
actually work depend on whether PATH_INFO and mod_rewrite is enabled  
on the server. Since this can't be detected from PHP, we have this  
"pretty_url" configuration that tells Horde which kind of URLs to use.  
This is only used for *displaying* the URLs to the user. It doesn't  
have any influence on whether they actually work or not. The  
adminstrator has to take care that the configuration matches the  
capabilities of the web server.
+In horde/rpc.php for example we support all 3 versions. If they  
actually work depend on whether PATH_INFO and mod_rewrite is enabled  
on the server. Since this can't be detected from PHP, we have this  
"pretty_url" configuration that tells Horde which kind of URLs to use.  
This is only used for **displaying** the URLs to the user. It doesn't  
have any influence on whether they actually work or not. The  
adminstrator has to take care that the configuration matches the  
capabilities of the web server.