Looks like you're after the Application_BeginRequest event which is raised 

by every request to the server (after Application_AuthenticateRequest and 

after Application_AuthorizeRequest).



good luck,

Arthur Gaisin



> It seems to me that authentication HAS 

> to occur before a web request is served.

> 

> Otherwise...why authenticate ?

> 

> Bry is, apparently, looking for an event after the page 

> has been requested, and the user has been authenticated,

> but before the page is loaded.

> 

> I haven't checked it out...but maybe OnInit ?

> ( if used within a control... )

> 

> regards,

> 

> 

> Juan

> ===

> 

> ----- Original Message ----- 

> From: "Thomas Tomiczek" <t.tomiczek@t...>

> To: "ASP+" <aspx@p...>

> Sent: Wednesday, June 20, 2001 5:36 AM

> Subject: [aspx] RE: asp.net session state

> 

> 

> George,

> 

> This event is fired when the session is CREATED, not when a page is

> requested.

> 

> On the original request, he wanted to READ the session data WHILE

> ASP.Net is in the handling of a Page request BEFORE the page is actually

> requested.

> 

> Bry, I have the same problem. It looks like not, sadly. The

> Authentificator seems to fire before the session module has initialized

> the session into the request's context.

> 

> Regards

> 

> Thomas

> 

> -----Original Message-----

> From: George Saliba [mailto:georges@c...] 

> Sent: Dienstag, 19. Juni 2001 00:39

> To: ASP+

> Subject: [aspx] RE: asp.net session state

> 

> Try Session_OnStart in your global.asax file i think.

> 

> George Saliba

> 

> -----Original Message-----

> From: Bry Pickett [mailto:bryp@g...]

> Sent: Monday, June 18, 2001 3:49 PM

> To: ASP+

> Subject: [aspx] RE: asp.net session state

> 

> 

> Thanks for this response.  I'm aware you can get to session state in 

> Page_Load.  

> 

> I'd like to know if session state is available 'further up the request 

> pipeline' (ie, before the Page_Load event).  If so, which event?

> 

> Thanks.

>