> A little more potentially useful information: > The 403 forbidden message that comes up when I try to access an https:// URL > also says: > "Additionally, a 403 Forbidden error was encountered while trying to use an > ErrorDocument to handle the request." > > So apparently Apache is *applying* the ErrorDocument directive to https:// > requests, it's just not able to find the /banned_ip.php file when doing so. No, not "not able to find". How did you "ban" the IP and how do you expect Apache to be able to serve the errordocument for the banned IP? > > So since my directive says > ErrorDocument 403 /banned_ip.php > how come Apache can find that file when giving a 403 error in response to an > https request, but not in response to an http request? Maybe you punched a hole in your config to allow access to the file, but only in the non-SSL vhost? -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|