I have an odd problem with an Apache 1.3 installation that I haven't started for a week or so.
On doing so, resources accessible via some Aliases are now all returning 403s, and AFAICT, I can no longer set up any new Aliases - resources accessible via the new Alias return 403. I'm almost totally certain that none of the config has been altered. Can anyone: 1) suggest what could have screwed up for Alias to break ? 2) let me know if there's any way I can get Apache to tell me why it wants to return a 403 for a particular resource ? This'd at least let me debug the problem a little more. -- Regards Stephen Collyer Netspinner Ltd --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
