"John DeGuenther" wrote:

> One thing you can do is to place the contents your home page inside an .ascx
> control and cache the output of the control. Your home page can include this
> control, which then satisfies the requirement to cache the page output.
>
> The home page (.aspx) will still generate an ASP.NET session, yet you still
> place minimal load on your web server by caching the control output.
>
> "Jon" wrote:
>
> > Our website caches a number of high-traffic pages, such as the home page. I
> > just noticed one behavior on our cached pages that's causing a problem- when
> > a user loads a cached page, an ASP.NET session is not started.
> >
> > Our code in the Session_Start event only fires when the user lands on the
> > first non-cached page. This is causing a lot of pain because we need to
> > track inbound referrer URLs and querystring values whenever a user lands
> > anywhere on our website from another domain.
> >
> > Is there any way to configure a cached page so that when users land on it a
> > session_start event will be fired?
> >