ansaurus

Question

Setting ResponseCode manually at CodeBehind fails with IIS7 and 2008 Server

Answer 1

A:

Your problem is probably that you have tried to set the Status Code (which counts as part of the Header) at some point after you've starting sending the Body of the response i.e. your pages contents - in your case the message.

To solve this you can try setting Response.Buffer to true and then if you have to set a 404/500 response code then call Response.Clear() before setting the response code.

Note that if you are sending a 404/500 then there should generally be no body to the response (although the HTTP spec does allow for it)

RobV 2009-09-07 14:38:30

i set the StatusCode @ OnLoad (where I contact my Web Service). Output of the page is generelly made in the Render method. I do not want to clear my initial response, which is a normal result page, just with a different message.

Andreas Niedermair 2009-09-08 05:42:09

have you tried just turning on Response.Buffer (but not clearing the response) and seeing if that works?

RobV 2009-09-10 13:51:28

nope - I set this.Response.Buffer to true, did not help... I do never clear my response - just set the StatusCode.

Andreas Niedermair 2009-09-11 08:21:25

Answer 2

+2 A:

Hello,

have you tried this:

protected override void OnLoad(EventArgs e)
{
    base.OnLoad(e);
    this.Response.StatusCode = 404;

    Response.TrySkipIisCustomErrors = true;
}

HttpResponse.TrySkipIisCustomErrors Property (System.Web)

najmeddine 2009-09-11 12:40:12

hehe ... nope - not yet ... i will give it a try tomorrow!

Andreas Niedermair 2009-09-13 20:28:01

works like charm!

Andreas Niedermair 2009-09-14 05:35:54

glad for you!

najmeddine 2009-09-14 08:12:01

ansaurus

tags:

views:

answers:

Setting ResponseCode manually at CodeBehind fails with IIS7 and 2008 Server

related questions