AuthenticateRequest event

by

It seems that the FormsAuthenticationModule gets handled first. This module is normally earlier than any custom module in the ASP.NET pipeline, so when AuthenticateRequest is fired, FormsAuthenticationModule will get called first, do its job and then your module’s event handler will be called.

If you really want to dig deep into this, I suggest trying to debug the ASP.NET code yourself. Here is a post how to set up your VS:

http://weblogs.asp.net/scottgu/archive/2008/01/16/net-framework-library-source-code-now-available.aspx

EDIT: I was able to confirm this behavior by setting up a web project with custom module and event handlers in Global.asax. Take a look at the source code of HttpApplication.InitInternal, the order of initialization is as follows:

  • initialization of integrated modules: FormsAuthenticationModule hooks up to HttpApplication.AuthenticateRequest event
  • initialization of custom modules: custom module hooks up to HttpApplication.AuthenticateRequest event
  • initialization of Global class (global.asax): here we hook up to the AuthenticateRequest event
  • HttpApplication.InitInternal searches for methods on Global class following the specific name pattern (e.g. Application_AuthenticateRequest), matches them to event and hooks up

After the initialization, when the AuthenticateRequest fires, the event handlers are called in the order they where initialized, so:

  • FormsAuthenticationModule.AuthenticateRequest event handler
  • CustomModule.AuthenticateRequest event handler
  • Global.AuthenticateRequest event handler
  • Global.Application_AuthenticateRequest method

Unless I missed something, there is no mechanism for stopping the event handlers to fire, so no matter what the result of FormsAuthenticationModule.AuthenticateRequest, the next handlers will still be called. I hope that helps.

More Related Contents:

  1. Forms Authentication across Sub-Domains
  2. .NET Core Identity Server 4 Authentication VS Identity Authentication
  3. Custom Authentication in ASP.Net-Core
  4. How do I log a user out when they close their browser or tab in ASP.NET MVC?
  5. how to generate a unique token which expires after 24 hours?
  6. ASP.NET Identity Cookie across subdomains
  7. How can I handle forms authentication timeout exceptions in ASP.NET?
  8. Simple JWT authentication in ASP.NET Core 1.0 Web API
  9. Storing more information using FormsAuthentication.SetAuthCookie
  10. Forms Authentication understanding context.user.identity
  11. ASP.NET Core Web API Authentication
  12. Built-in helper to parse User.Identity.Name into Domain\Username
  13. How to get the URL of the current page in C# [duplicate]
  14. Display custom error page when file upload exceeds allowed size in ASP.NET MVC
  15. {version} wildcard in MVC4 Bundle
  16. Get the current user, within an ApiController action, without passing the userID as a parameter
  17. Running an asynchronous operation triggered by an ASP.NET web page request
  18. Are static variables thread-safe? C#
  19. When Should I Use Response.Redirect(url, true)?
  20. Could not load file or assembly ‘System.Web.Helpers, error on IIS 8
  21. Why does HttpWebRequest throw an exception instead returning HttpStatusCode.NotFound?
  22. Multiple signalR connections/hubs on your website
  23. ASP.NET – AppDomain.CurrentDomain.GetAssemblies() – Assemblies missing after AppDomain restart
  24. WebAPI Request Streaming support
  25. Opposite of [compare(” “)] data annotation in .net?
  26. Can I reuse HttpWebRequest without disconnecting from the server?
  27. Conditional Logic in ASP.net page
  28. Cast an Anonymous Types in Object and retrieve one Field
  29. What are some alternatives to ReSharper? [closed]
  30. See if user is part of Active Directory group in C# + Asp.net

Leave a Comment