At 6:48 AM +1100 19/3/01, Howard Lowndes wrote:
><Directory /var/www/guest/LANNet>
> Redirect permanent /var/www/guest/LANNet/GIMP_Manual
>http://manual.gimp.org/manual/GUM/GUM.html
></Directory>
You shouldn't be using a full Unix file system path in a redirect
directive -- the path should be relative to server-root.
Also, the file you're redirecting from does not need to exist on your
system. Redirect also considers subdirectories of the redirected path, so
you generally redirect an old directory on your server to the new directory
containing the same stuff on a new server.
I would think this would do what you want:
Redirect permanent /guest/LANNet/GIMP_Manual http://manual.gimp.org/manual/GUM
It would redirect
http://www.lannet.com.au/guest/LANNet/GIMP_Manual/something.html
to
http://manual.gimp.org/manual/GUM/something.html
>From the Apache manual:
Redirect directive
Syntax: Redirect [ status ] url-path url
...
The Redirect directive maps an old URL into a new one. The new
URL is returned to the client which attempts to fetch it again
with the new address. Url-path a (%-decoded) path; any requests
for documents beginning with this path will be returned a
redirect error to a new (%-encoded) url beginning with url.
Example:
Redirect /service http://foo2.bar.com/service
If the client requests http://myserver/service/foo.txt, it will be told to
access http://foo2.bar.com/service/foo.txt instead.
...R.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
