Really? That has not been my experience. There are several sites on this server and for some it works fine accessing the site from the server using the domain. When I access from the server I get a complete error message and from outside I get the redirect.
It just seems that on this one site that I have problems. At any rate, I plan to look into the points that Juan made so hopefully I can track down the problem. It is odd...
It probably does not help that there is a mixture of asp, aspx, html and other stuff on here.
- Ron
"George" <no****@hotmail.com> wrote in message news:OF**************@TK2MSFTNGP14.phx.gbl...
It works depending on the way how you access your site.
Even when you are running locally you need to access it by 127.0.0.1 and not by
www.mysite.com (or ip address)
The site would not know how you are accessing it (localy or not) if you are using inet name or ip address
George.
"Ron Weldy" <ro******@msn.com> wrote in message news:O$****************@TK2MSFTNGP14.phx.gbl...
I am working on a website that someone else has set up. They have a
web.config file with a customerrors element that points the error handling
to a special aspx page.
<customErrors mode="RemoteOnly" defaultRedirect="/customerrors/500.aspx">
<error statusCode="404" redirect="/customerrors/404.html" />
</customErrors>
When running pages directly on the server it still redirects when a error
occurs, even though it should not judging by the "RemoteOnly" setting. I
have also tried just setting the mode to "Off" but that does not change the
behavior either. What could I be missing? I have looked for other config
file but have found none. Anybody got any ideas why I cannot turn off the
error handling, or where I can look to figure out what is going on?