Global.ASAX changing URL


Ad

Advertisements

G

Guest

Hi All,
i do have an website with the URLhttp://localhost/application/ASEAN-ANZ,

Once i hit the application, it goes to the Global.asax.

but after that if i tried to change the URLhttp://localhost/application/en-US,

the global.asax is not fired.

Does any body has any idea why this is not fired

Thanks in Advance

Thomso

which event is not fired?
 
J

Juan T. Llibre

re:
Does any body has any idea why this is not fired

The Global.asax file may contain the following events:

- Application_Init:
Fired when an application initializes or is first called.
It's invoked for all HttpApplication object instances.

Only fires once, when the application starts.

- Application_Disposed:
Fired just before an application is destroyed.
This is the ideal location for cleaning up previously used resources.

It's fired only once during an application's lifetime.

- Application_Error:
Fired when an unhandled exception is encountered within the application.

- Application_Start:
Fired when the first instance of the HttpApplication class is created.
It allows you to create objects that are accessible by all HttpApplication instances.

Only fires once, when the application starts.

- Application_End:
Fired when the last instance of an HttpApplication class is destroyed.

It's fired only once during an application's lifetime.

- Application_BeginRequest:
Fired when an application request is received.
It's the first event fired for a request, which is often a page request (URL) that a user enters.

Does your code reside in this event ?

- Application_EndRequest:
The last event fired for an application request.

Does your code reside in this event ?

- Application_PreRequestHandlerExecute:
Fired before the ASP.NET page framework begins executing
an event handler like a page or Web service.

Does your code reside in this event ?

- Application_PostRequestHandlerExecute:
Fired when the ASP.NET page framework is finished executing an event handler.

Does your code reside in this event ?

- Applcation_PreSendRequestHeaders:
Fired before the ASP.NET page framework sends HTTP headers to a requesting client (browser).

Does your code reside in this event ?

- Application_PreSendContent:
Fired before the ASP.NET page framework sends content to a requesting client (browser).

Does your code reside in this event ?

- Application_AcquireRequestState:
Fired when the ASP.NET page framework gets the current state
(Session state) related to the current request.

Does your code reside in this event ?

- Application_ReleaseRequestState:
Fired when the ASP.NET page framework completes execution of all event handlers.
This results in all state modules to save their current state data.

Does your code reside in this event ?

- Application_ResolveRequestCache:
Fired when the ASP.NET page framework completes an authorization request. It allows
caching modules to serve the request from the cache, thus bypassing handler execution.

Does your code reside in this event ?

- Application_UpdateRequestCache:
Fired when the ASP.NET page framework completes handler execution to allow
caching modules to store responses to be used to handle subsequent requests.

Does your code reside in this event ?

- Application_AuthenticateRequest:
Fired when the security module has established the current user's identity as valid.
At this point, the user's credentials have been validated.

Does your code reside in this event ?

- Application_AuthorizeRequest:
Fired when the security module has verified that a user can access resources.

Does your code reside in this event ?

- Session_Start:
Fired when a new user visits the application Web site.

Does your code reside in this event ?

- Session_End:
Fired when a user's session times out, ends, or they leave the application Web site.

Does your code reside in this event ?

In which of the above-listed events does your code reside ?




Juan
====
 
Ad

Advertisements

T

thomson

re:


TheGlobal.asaxfile may contain the following events:

- Application_Init:
Fired when an application initializes or is first called.
It's invoked for all HttpApplication object instances.

Only fires once, when the application starts.

- Application_Disposed:
Fired just before an application is destroyed.
This is the ideal location for cleaning up previously used resources.

It's fired only once during an application's lifetime.

- Application_Error:
Fired when an unhandled exception is encountered within the application.

- Application_Start:
Fired when the first instance of the HttpApplication class is created.
It allows you to create objects that are accessible by all HttpApplication instances.

Only fires once, when the application starts.

- Application_End:
Fired when the last instance of an HttpApplication class is destroyed.

It's fired only once during an application's lifetime.

- Application_BeginRequest:
Fired when an application request is received.
It's the first event fired for a request, which is often a page request (URL) that a user enters.

Does your code reside in this event ?

- Application_EndRequest:
The last event fired for an application request.

Does your code reside in this event ?

- Application_PreRequestHandlerExecute:
Fired before the ASP.NET page framework begins executing
an event handler like a page or Web service.

Does your code reside in this event ?

- Application_PostRequestHandlerExecute:
Fired when the ASP.NET page framework is finished executing an event handler.

Does your code reside in this event ?

- Applcation_PreSendRequestHeaders:
Fired before the ASP.NET page framework sends HTTP headers to a requesting client (browser).

Does your code reside in this event ?

- Application_PreSendContent:
Fired before the ASP.NET page framework sends content to a requesting client (browser).

Does your code reside in this event ?

- Application_AcquireRequestState:
Fired when the ASP.NET page framework gets the current state
(Session state) related to the current request.

Does your code reside in this event ?

- Application_ReleaseRequestState:
Fired when the ASP.NET page framework completes execution of all event handlers.
This results in all state modules to save their current state data.

Does your code reside in this event ?

- Application_ResolveRequestCache:
Fired when the ASP.NET page framework completes an authorization request. It allows
caching modules to serve the request from the cache, thus bypassing handler execution.

Does your code reside in this event ?

- Application_UpdateRequestCache:
Fired when the ASP.NET page framework completes handler execution to allow
caching modules to store responses to be used to handle subsequent requests.

Does your code reside in this event ?

- Application_AuthenticateRequest:
Fired when the security module has established the current user's identity as valid.
At this point, the user's credentials have been validated.

Does your code reside in this event ?

- Application_AuthorizeRequest:
Fired when the security module has verified that a user can access resources.

Does your code reside in this event ?

- Session_Start:
Fired when a new user visits the application Web site.

Does your code reside in this event ?

- Session_End:
Fired when a user's session times out, ends, or they leave the application Web site.

Does your code reside in this event ?

In which of the above-listed events does your code reside ?

Juan
====
"thomson" <[email protected]> escribió en el mensaje









- Show quoted text -

Hi,
Its the Session_Acquire RequestState , Event, any insights


Thanks

Thomson
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top