On Thu, Jan 08, 2004 at 09:44:41PM -0600, James A Baker wrote: > >>ScriptAlias / "/var/www/cgi-bin/" ... > C) If you really know what you're doing, you might find a good way to > set up a redirect or mod_rewrite rule for the "/" path that forwards > people to the sqwebmail URL automatically... *AND* doesn't recursively > catch itself building an ever longer, infinitely looping, path > request... but that might be impossible without using 2 domain names -- > I'm not entirely sure.
The simplest solution is to go back to a standard /cgi-bin/sqwebmail URL, then create index.html in the top of your docroot which looks something like: <html> <head> <meta http-equiv="refresh" content="0; url=/cgi-bin/sqwebmail"> </head> <body> <p>If your browser does not refresh automatically, please <a href="/cgi-bin/sqwebmail">click here</a> to continue</p> </body> </html> Or if you have .asis enabled, you can create index.asis, something like (not tested): 302 Moved Temporarily Location: http://myserver.com/cgi-bin/sqwebmail <html> <body> <p>If your browser does not refresh automatically, please <a href="/cgi-bin/sqwebmail">click here</a> to continue</p> </body> </html> which should work on older browsers without meta tags, and may avoid flashing the annoying message on the screen briefly. If you don't like seeing "cgi-bin" in your URLs then try setting up an alias for the binary: ScriptAlias /webmail /var/www/cgi-bin/sqwebmail Then http://yourhost.com/webmail is your sqwebmail app, and you can still use an index file to redirect http://yourhost.com/ to http://yourhost.com/webmail All the above solutions have the important property that http://yourhost.com/images/... still works to serve normal HTML documents, needed for sqwebmails CSS and graphics. Brian.
