Re: Page shown after an error by jeff
jeff
Wed Oct 20 15:47:27 CDT 2004
On Wed, 20 Oct 2004 14:29:12 -0400, "Ragnar Midtskogen"
<ragnar_ng@newsgroups.com> wrote:
>Thanks Jeff,
>
>> Perhaps as simple as a link or something that the browser resolves,
>> which points back to the live system due to the name resolution.
>
>If you mean a link to the live server in the page that causes the error, or
>in a page that called the offending page, I have not found any.
>
>> Doesn't mean your backup server is broken, just that it's not live.
>
>???
>The server is live in one sense, it is on the Internet, but with a different
>URL.
Then it's not an exact copy. Anything referencing the server will
naturally resolve to the version the code was written on/for.
You may have more help tracking this down by posting an actual error
in an ASP group.
Jeff
>Ragnar
>
>"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
>news:4177c0d2.549005848@msnews.microsoft.com...
>> On Tue, 19 Oct 2004 18:43:43 -0400, "Ragnar Midtskogen"
>> <ragnar_ng@newsgroups.com> wrote:
>>
>>>Hello,
>>>
>>>I am trying to set up a backup server for one of our Web sites and I am
>>>having a puzzling problem with error handling.
>>>
>>>All the files from the live server has been copied to the new machine and
>>>at
>>>this point almost everything is working OK.
>>>
>>>However, some asp pages still produce errors, and what I can not figure
>>>out
>>>is what happens after an error.
>>>The site has a home page, and when an error occurs I would expect to end
>>>up
>>>on the default page, but it ends up on the deault page of the live site.
>>>
>>>I have gone through the properties of the Web site, including custom
>>>errors,
>>>and can not find anything that would cause this behavior.
>>
>> Perhaps as simple as a link or something that the browser resolves,
>> which points back to the live system due to the name resolution.
>> Doesn't mean your backup server is broken, just that it's not live.
>>
>> Jeff
>