I think it doesn't have to be the 403 page that Apache would have sent, it may just be one you made yourself, and which somewhat looks like a 403 error page.
Besides, as error pages can always be customized, there's no need for it to ever be the real 403 page. | [reply] [Watch: Dir/Any] |
I had read the other thread, but didn't follow everything, given my knowledge level...
So if the header contains the 403 code, then a bot might hopefully interpret that correctly and go away (hopefully!)?
BTW, There are certain types of data errors that I want to reply with this fake reply, while for other 'normal' errors, I have a nice formatted page that I use, so determining which to send needs to occur within my CGI script, as I see it.
I'm also presuming that I could output a minimal "Access Forbidden" page with this response code, so a browser user would see that? As the standard config error page (I believe) gives an email addr, which I don't want to provide in this case. | [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |