>Request.UrlReferer will be null when the page is accessed directly through the browser. On the other hand, if the page is being requested from other page (by a link, for example) then UrlReferer will have a valid instance.
>
>Just for the record, the Request.UrlReferer property gets its value from the HTTP request header. This value is optional and might be situations when you really won't receive it.

For me, no matter how the page is called, this is always empty. As it was with the HTTP header, we cannot rely on that. I will look for a custom way of keeping that value from page to page. I have a framework application object and will use that for that purpose.

Thanks