| Author |
 Topic  |
|
|
Shaggy
Support Moderator
Ireland
6780 Posts |
 Posted - 02 April 2008 : 05:46:16
|
In yet another first, I've created some pages to handle 403, 404 and 500 errors encountered on one of my sites but I'm having a problem with the 500 error page. If the error occurs after anything else has been written on the page then the 500.asp file is written after that, causing some funky HTML/XML errors. You can see an example of what's happening here <link removed /> (source). This <link removed /> is how it should look (source). I've already tried setting response.buffer to true so I'm guessing, maybe, it's something I've missed in IIS.
|
 Search is your friend
“I was having a mildly paranoid day, mostly due to the
fact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.” |
Edited by - Shaggy on 07 April 2008 04:59:44 |
|
|
Shaggy
Support Moderator
Ireland
6780 Posts |
Posted - 04 April 2008 : 07:39:11
|
Bumpage! (Sorry)
|
Search is your friend
“I was having a mildly paranoid day, mostly due to the
fact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.” |
 |
|
|
pdrg
Support Moderator
United Kingdom
2897 Posts |
Posted - 05 April 2008 : 13:56:12
|
Would response.clear help?
Also, instead of on error resume next, could you just handle the error? |
Edited by - pdrg on 05 April 2008 13:57:34 |
|
|
|
Shaggy
Support Moderator
Ireland
6780 Posts |
Posted - 07 April 2008 : 04:57:34
|
quote:
Originally posted by pdrg
Would response.clear help?
*bounces head off desk* Of course it would - silly Shaggy!
|
Search is your friend
“I was having a mildly paranoid day, mostly due to the
fact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.” |
|
|
| |
Topic |
|
Topic Locked
