I would actually suggest against sending a 403 or some other HTTP
access denied because the crawlers may act adversly. The redirection
is a good idea. The crawlers will not care as long as it is a
temporary redirect, not a permanent one. Try something like this:
Response.StatusCode = 302
Response.Status = "302 Moved Temporarily"
Response.AddHeader("Location", "/Unauthorized.aspx") ' Note: "/
Unauthorized.aspx" is just an example
Response.End()
Hope this helps.
On Jul 3, 10:49*am, coconet <coco...@community.nospamwrote:
I don't want to do that because a crawling bot might be hitting the
page too. I want to show unauthorized access early in the HTTP
communication process, low level. Can I do that from within a ASPX
page?
On Wed, 2 Jul 2008 20:51:29 -0700 (PDT), Anoj <sutradh...@gmail.com>
wrote:
Another idea could be redirecting the user to a custom page showing
access denied message.
/Anoj
[www.TheTechHub.com]
On Jul 3, 1:01*am, coconet <coco...@community.nospamwrote:
I want to block access to my ASP.NET 2.0 web page if the time is
between 3:00 and 4:00. I know how to do the date math - is it proper
to throw an UnauthorizedAccessException at that time? I want to pass
an "access denied" back to the browser but am not sure if that will
work.
Thanks