>>Sure it will. A redirected page is another HTTP request. The event will fire both for the original page that Response.Redirect() is called on and then again in the page that is redirected to.
>>
>>It won't fire if you use Server.Transfer() to go to another page because that stays in the same request context.
>
>Thanks, I discovered this morning that it was going in fact in there (in both events) also in a redirect. There was something in my framework I had to adjust. But, during the last week, I was able to learn more about the factory design and how it can be better to use than the global.asax, based on specific designs. So, if I have ever a need to make that approach evolve more, I will be sure to consider the factory for such needs.

I'm not really sure how a factory is going help you in capturing what essentially are system events. Global.asax is the low level ASP.NET pipeline and every thing fires through that. You can abstract out global.asax code by using HttpModules which basically allow you to capture events independnently of the application and reuse that functionality, but that's still within the context of an event driven approach.