Custom error page handling provides false positive

[GoogleCodeExporter]

What steps will reproduce the problem?
Surf to a web page that does not exist.

What is the expected output?
The user agent should receive a 404 (Not Found) status as per the HTTP 
specification.

What do you see instead?
The user agent sees a 302 (Found) followed by a 200 (OK), which is a false 
positive. The page does not exist and so should return a 404. See attached 
file for a detailed transaction.

Please provide any additional information below.
Due to the way the error-handling is setup in Global.asax, all error 
conditions will end re-direction (i.e. 302 followed by 200). The false 
positive here is that the user agent are being deceived into thinking that 
the final error page is a valid response (albeit temporary) for the 
original request. For more information and a possible way of getting 
around this, see http://groups.google.com/group/elmah/msg/980ecdc48fe86065.

Original issue reported on code.google.com by azizatif on 26 Sep 2007 at 4:28

Attachments:

• log.txt

[GoogleCodeExporter]

Good advice Atif, I'll implement your recommendations.

Original comment by gavinjo...@gmail.com on 26 Sep 2007 at 4:35

• Changed state: Accepted
• Added labels: Component-UI

[GoogleCodeExporter]

Original comment by gavinjo...@gmail.com on 26 Sep 2007 at 4:38

[GoogleCodeExporter]

Fixed in r440

Original comment by azizatif on 27 Sep 2007 at 5:09

• Changed state: Fixed