A site I'm working on has an httpmodule that executes on every page request to determine if certain cookies need to be changed to alter the user's state. After a page (tab) has been cached that page is always returned from cache and the httpmodule doesn't have an opportunity to execute to determine if it needs to alter any cookies.

I tried moving pageblaster around in my web.config, before and after iFinity and even to the beginning and end of the relevant sections and it still never executes.

Have you encountered this and do you know of a fix?

Thanks tons,

Brian Strickland

Fyi this httpmodule is executing on context.PostAcquireRequestState with iRequiresSessionState, we had to do this so that session and request were fully available. It used to use context.BeginRequest. I wonder if it might execute on BeginRequest but with no Request or Session available that wouldn't help.

PageBlaster sends back a cache file in the ResolveRequestCache event of the pipeline. At that point it completes the app cycle, so you'll need to perform other work earlier in the cycle if you want it to be done before a cached page is sent back. You might try putting it in AuthorizeRequest where there should be a session available.

ASP.Net Pipeline

#1 Internal step to validate request. Protects against malicious attacks exploiting path canonicalization
#2 Internal step to perform URL mapping (if the URL mapping feature is enabled)
#3 Fire BeginRequest event
#4 Fire AuthenticateRequest event
#5 Fire DefaultAuthentication internal event
#6 Fire PostAuthenticateRequest event
#7 Fire AuthorizeRequest event
#8 Fire PostAuthorizeRequest event
#9 Fire ResolveRequestCache event
#10 Fire PostResolveRequestCache event
#11 Internal step to determine the IHttpHandler to process the current request (this is when the page compilation takes place)
#12 Fire PostMapRequestHandler event
#13 Fire AcquireRequestState event
#14 Fire PostAcquireRequestState event
#15 Fire PreRequestHandlerExecute event
#16 Internal step to execute the IHttpHandler (call its ProcessRequest method) for the current request. The handler is determined at step #11
#17 Fire PostRequestHandlerExecute event
#18 Fire ReleaseRequestState event
#19 Fire PostReleaseRequestState event
#20 Internal step to perform response filtering (only if HttpResponse.Filter is installed)
#21 Fire UpdateRequestCache event
#22 Fire PostUpdateRequestCache event
#23 Fire EndRequest event. This is the only event that is guaranteed to be fired for each request