Description:
------------
Livedocs's htaccess file works in a very strange way, by rewriting to a non-existent file, letting Apache's error document forward it to index.php, and then handling it. This is confusing, and doesn't work in certain cases (in said cases, the user consistently gets the File protocols and wrappers page). A better htaccess file:

Index: .htaccess.in
===================================================================
RCS file: /repository/livedocs/.htaccess.in,v
retrieving revision 1.3
diff -u -r1.3 .htaccess.in
--- .htaccess.in	4 Oct 2004 06:41:13 -0000	1.3
+++ .htaccess.in	2 Apr 2007 21:16:59 -0000
@@ -1,6 +1,6 @@
 RewriteEngine on
-RewriteRule @WEBBASE@.*\.[^h][^t][^m][^l]$ @WEBBASE@$1.html
-ErrorDocument 404 @WEBBASE@index.php
+RewriteCond %{REQUEST_FILENAME} !-f [OR]
+RewriteCond %{QUERY_STRING} purge=1
+RewriteRule ^([A-Za-z_]+)/([A-Za-z._-]+)\.html$ @WEBBASE@index.php?l=$1&q=$2 [L,QSA]
 DirectoryIndex index.php
 php_value default_charset "UTF-8"
 AddCharset UTF-8 .html

In this case, we specifically match the HTML file, and directly refer to the index.php script, instantiating the correct l and q parameters. A user can also pass ?purge=1 to the HTML file to force it to be regenerated, and the system intelligently detects when the file does not exist using the -f command.