发表新帖
发表新帖

Server cannot set status after HTTP headers have been sent IIS7.5

后端 未结
关注
10 886
爱一瞬间的悲伤
爱一瞬间的悲伤 2020-11-27 12:32

Sometimes I get exception in my production environment:

  • Process information
    • Process ID: 3832
    • Pr
相关标签:
10条回答
  • 甜味超标
    2020-11-27 12:39

    Just to add to the responses above. I had this same issue when i first started using ASP.Net MVC and i was doing a Response.Redirect during a controller action:

    Response.Redirect("/blah", true);

    Instead of returning a Response.Redirect action i should have been returning a RedirectAction:

    return Redirect("/blah");
    0 讨论(0)
  • 不知归路
    2020-11-27 12:42

    I'll broadly agree with Vagrant on the cause:

    1. your action was executing, writing markup to response stream
    2. the stream was unbuffered forcing the response headers to get written before the markup writing could begin.
    3. Your view encountered a runtime error
    4. Exception handler kicks in trying to set the status code to something else non-200
    5. Fails because the headers have already been sent.

    Where I disagree with Vagrant is the "cause no errors in binding" remedy - you could still encounter runtime errors in View binding e.g. null reference exceptions.

    A better solution for this is to ensure that Response.BufferOutput = true; before any bytes are sent to the Response stream. e.g. in your controller action or On_Begin_Request in application. This enables server transfers, cookies/headers to be set etc. right the way up to naturally ending response, or calling end/flush.

    Of course also check that buffer isn't being flushed/set to false further down in the stack too.

    MSDN Reference: HttpResponse.BufferOutput

    0 讨论(0)
  • 伪装坚强ぢ
    2020-11-27 12:44

    I had the same issue with setting StatusCode and then Response.End in HandleUnauthorizedRequest method of AuthorizeAttribute

    var ctx = filterContext.HttpContext;
ctx.Response.StatusCode = (int)HttpStatusCode.Forbidden;
ctx.Response.End();

    If you are using .NET 4.5+, add this line before Response.StatusCode

    filterContext.HttpContext.Response.SuppressFormsAuthenticationRedirect = true;

    If you are using .NET 4.0, try SuppressFormsAuthenticationRedirectModule.

    0 讨论(0)
  • 有刺的猬
    2020-11-27 12:44

    I remember the part from this exception : "Cannot modify header information - headers already sent by" occurring in PHP. It occurred when the headers were already sent in the redirection phase and any other output was generated e.g.:

    echo "hello"; header("Location:http://stackoverflow.com");

    Pardon me and do correct me if I am wrong but I am still learning MS Technologies and I was trying to help.

    0 讨论(0)
  • 陌清茗
    2020-11-27 12:48

    The HTTP server doesn't send the response header back to the client until you either specify an error or else you start sending data. If you start sending data back to the client, then the server has to send the response head (which contains the status code) first. Once the header has been sent, you can no longer put a status code in the header, obviously.

    Here's the usual problem. You start up the page, and send some initial tags (i.e. <head>). The server then sends those tags to the client, after first sending the HTTP response header with an assumed SUCCESS status. Now you start working on the meat of the page and discover a problem. You can not send an error at this point because the response header, which would contain the error status, has already been sent.

    The solution is this: Before you generate any content at all, check if there are going to be any errors. Only then, when you have assured that there will be no problems, can you then start sending content, like the tag.

    In your case, it seems like you have a login page that processes a POST request from a form. You probably throw out some initial HTML, then check if the username and password are valid. Instead, you should authenticate the user/password first, before you generate any HTML at all.

    0 讨论(0)
  • 长发绾君心
    2020-11-27 12:49

    I apologize, but I'm adding my 2 cents to the thread just in case anyone has the same problem.

    • I used Forms Authentication in my MVC app
    • But some controller-actions were "anonymous" i.e. allowed to non-authenticated users
    • Sometimes in those actions I would still want users to be redirected to the login form under some condition
    • to do that - I have this in my action method: return new HttpStatusCodeResult(401) - and ASP.NET is super nice to detect this, and it redirects the user to the login page! Magic, right? It even has the proper ReturnUrl parameter etc.

    But you see where I'm getting here? I return 401. And ASP.NET redirects the user. Which is essentially returns 302. One status code is replaced with another.

    And some IIS servers (just some!) throw this exception. Some don't. - I don't have it on my test serevr, only on my production server (ain't it always the case right o_O)

    I know my answer is essentially repeating what's already said here, but sometimes it's just hard to figure out where this overwriting happens exactly.

    0 讨论(0)
 看不清?
提交回复
热议问题