Browser refresh forgets the original request

[Jaikanth Sithambaranathan via .NET 247]

The problem is in the result page in which i can scroll throughthe contents of the result set 100 at a time. I call the resultpage from a filter page where i accept filter on results to bedisplayed. When i get to the result page by submitting (on clickof a button) from within the filter page or result page theserver understands the calling page using Request.UrlReferrerproerty. When I refresh the page using browser Refresh button,UrlReferrer property forgets who is the calling page. It iseither null or gives the url of the containing page. The filterand result page are contained within a parent page. Parent pagecontains two Iframes (one to display application header andother to display the content section).

Do anyone have an idea of what is happening to UrlReferrerproperty? Is there a way in which i can make the webserverremember the url calling sequence?

Thanks

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>Z9mpnJROzkiz7BqYCChHXA==</Id>

[jasonkester]

Jaikanth Sithambaranathan via .NET 247 wrote:

When i get to the result page by submitting (on click of a button) from within the filter page or result page the server understands the calling page using Request.UrlReferrer proerty. When I refresh the page using browser Refresh button, UrlReferrer property forgets who is the calling page.
Do anyone have an idea of what is happening to UrlReferrer property?

Sounds like you already answered your question. UrlReferrer gets
populated with the page you were on when you requested the page you're
currently rendering. On your initial request, that would be the page
you came from. When you then refresh the page, UrlReferrer is
correctly telling you that you are standing on yourpage.aspx, and
asking to display yourpage.aspx.

If you want to keep the original Referrer value alive, you'll need to
store it somewhere. Sessions come to mind as a mechanism that would
work, but really, you should look to fix the architecture issues that
got you to this point.

Good luck!
Jason
http://www.expatsoftware.com/

[bruce barker]

you should avoid use of UrlReferrer as many proxy server will strip it from
the request.

-- bruce (sqlwork.com)
"Jaikanth Sithambaranathan via .NET 247" <an*******@dotnet247.com> wrote in
message news:Og**************@TK2MSFTNGP14.phx.gbl...
The problem is in the result page in which i can scroll through the contents
of the result set 100 at a time. I call the result page from a filter page
where i accept filter on results to be displayed. When i get to the result
page by submitting (on click of a button) from within the filter page or
result page the server understands the calling page using
Request.UrlReferrer proerty. When I refresh the page using browser Refresh
button, UrlReferrer property forgets who is the calling page. It is either
null or gives the url of the containing page. The filter and result page are
contained within a parent page. Parent page contains two Iframes (one to
display application header and other to display the content section).

Do anyone have an idea of what is happening to UrlReferrer property? Is
there a way in which i can make the webserver remember the url calling
sequence?

Thanks

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>Z9mpnJROzkiz7BqYCChHXA==</Id>