Skip to main content

Asp.Net – Creating a new custom HTTP Module

An HTTP Module is a .NET class that executes with each and every page request. You can use an HTTP Module to handle any of the HttpApplication events that you can handle in the Global.asax file.

You are already familiar with some of the HTTP Modules like
  • FormsAuthenticationModule handles the Forms authentication
  • WindowsAuthenticationModule handles the Windows authentication
  • SessionStateModule manages the session state of ASP.net application
  • OutputCacheModule deals with output caching
  • ProfileModule used for interaction with user profiles

Each HTTP Module subscribes to one or more HttpApplication events. For example, when the HttpApplication object raises its AuthenticateRequest event, the FormsAuthenticationModule executes its code to authenticate the current user.

Below I have included a sample class which implements the IHttpModule interface

In the Init event I have created an EventHandler for the PostAuthorizeRequest event of Http Application

namespace AspNet
{
    public class CustomContentModule : IHttpModule
    {
        public void Init(HttpApplication app)
        {
         
            app.PostAuthorizeRequest += new EventHandler(SendRequest);
        }
        public void SendRequest(Object sender, EventArgs e)
        {
            HttpApplication app = (HttpApplication)sender;
            app.Response.Write("Hi content from HTTP Module
Pay my tax also !!!"
);
        }

        public void Dispose() { }
    }
}



You can use any of the following events of HTTP Application; the events are raised in the following order:

  1. BeginRequest
  2. AuthenticateRequest
  3. PostAuthenticateRequest
  4. AuthorizeRequest
  5. PostAuthorizeRequest
  6. ResolveRequestCache
  7. PostResolveRequestCache

      After the PostResolveRequestCache event and before the PostMapRequestHandler event, an event handler (which is a page that corresponds to the request URL) is created. When a server is running IIS 7.0 in Integrated mode and at least the .NET Framework version 3.0, the MapRequestHandler event is raised. When a server is running IIS 7.0 in Classic mode or an earlier version of IIS, this event cannot be handled.

  1. PostMapRequestHandler
  2. AcquireRequestState
  3. PostAcquireRequestState
  4.  PreRequestHandlerExecute

      The event handler is executed.

  1. PostRequestHandlerExecute
  2. ReleaseRequestState
  3. PostReleaseRequestState

      After the PostReleaseRequestState event is raised, any existing response filters will filter the output.

  1. UpdateRequestCache
  2. PostUpdateRequestCache
  3. LogRequest.

      This event is supported in IIS 7.0 Integrated mode and at least the .NET Framework 3.0
 
  1. PostLogRequest

      This event is supported IIS 7.0 Integrated mode and at least the .NET Framework 3.0
  1. EndRequest


After creating this class add the following entry in Web.config

            <httpModules>
                        <add name="CustomContentModule" type="AspNet.CustomContentModule"/>
            httpModules>

When you excute any page in this application HTTP Runtime will add the content from the HTTP module created by us. You can build on this to create more complex scenarious like custom authitication, generation.processing of data based on the paraametr availalle in the Http Application objects etc.

Comments

Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master -  http://www.theagileschool.com/2012/03/scrummasters-checklist-roles.html • Product Owner • Feature Team The PDCA cycle ( http://www.theagileschool.com/2012/05/pdca-scrum-or-agile-why-is-it-important.html  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ http://www.scrum.org/Scrum-Guides will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I