| 4:49 pm on Apr 6, 2003 (gmt 0)|
Use the ErrorDocument [httpd.apache.org] directive.
| 5:22 pm on Apr 6, 2003 (gmt 0)|
Helpful but the only viable option is using a full URL which isn't really a great idea in general and doesn't work for 401 errors.
I'll look into the matter further.
| 7:59 pm on Apr 6, 2003 (gmt 0)|
How about defining the errordocuments as if they existed in the subdomain's root, and then defining the error document as a symbolic link back to the site root directory? This way, you're working using a file-system view instead of a URL view, so you don't need any external redirects (which mess up the HTTP response codes).
| 8:16 pm on Apr 6, 2003 (gmt 0)|
That would work nicely. Now how do I create a symlink through FTP or on a Windows box? I don't think it's possible with the limited resources I have.
| 8:24 pm on Apr 6, 2003 (gmt 0)|
Can you use Telnet to log in?
If not, maybe you could create them as files, and ask your host's tech support to change them to symlinks for you. (The only advantage of creating them as files is to act as placeholders for the symlinks so that the techs can see they are in the right directory - might save some back-and-forth with them.)
| 8:31 pm on Apr 6, 2003 (gmt 0)|
Hmm... I'll have to look into that. Thanks again.