Modify Httpcontext.Current.User is breaking the Bundle Optimization

Question

Modify Httpcontext.Current.User is breaking the Bundle Optimization

Asked 8 years, 9 months ago

Viewed 65 times

2

I did several tests and I could see that by modifying the HttpContext.Current.User Application_PostAuthenticateRequest (Global.asax.Cs) I get an Internal Server Error in the concatenated/minified Bundle request.

Follows code quoted:

protected void Application_PostAuthenticateRequest( Object sender, EventArgs e )
    {
        HttpContext.Current.User = SessionManager.GetCurrentUser( Request );

        if (IsWebApiRequest())
        {
            HttpContext.Current.SetSessionStateBehavior( SessionStateBehavior.Required );
        }
    }

    private bool IsWebApiRequest()
    {
        return HttpContext.Current.Request.AppRelativeCurrentExecutionFilePath.StartsWith( WebApiConfig.UrlPrefixRelative );
    }

There is only the header of the request with error. What is the real error?

– Leonel Sanches da Silva

2015/12/14 at 21:16
The request does not generate an Http Response in the console. It generates an html with an Runtime error. https://gist.github.com/cbfranca/5b32461f6613486e3d11

– cbfranca

2015/12/14 at 21:22
A kick: I think for Bundling there is no user associated with the context. Have you tried debugging this event?

– Leonel Sanches da Silva

2015/12/14 at 21:27
1

That’s exactly what @Ciganomorrisonmendez. Obg

– cbfranca

2015/12/14 at 21:54

1 answer

Browser other questions tagged asp.net-mvc asp.net

You are not signed in. Login or sign up in order to post.

by cbfranca • 71 points · Answer 1 · 2015-12-14T21:54:09+00:00

The problem was that the SessionManager.GetCurrentUser( Request ); this null and when assigning to HttpContext.Current.User Bundle generated an exception.