Executing server.transfer to another page does not retrieve the cached version of that page. Is this by design? Response.Redirect does retrieve the cached version. From what I've read server.transfer happens on the server and response.redirect happens on the
client does this make a difference whether or not the server retreives the cached version of the page? Is it possible to somehow retrieve the cached version of the page and display it on server.transfer? Why would I need to do this? I'm trying to create a
CMS somewhat similar to IBuySpy and DotNetNuke, but I've added in a feature which allows users to create "virtual directories" by modifying the 404 error page to do a server.transfer to a specific pageID. Thus if someone goes to http://mysite/myvirtualdirectory/
they are invisibly redirected to http://mysite/default.aspx?id=(mypageID), but what the user sees in the URL is http://mysite/myvirtualdirectory/. Then when they bookmark the page it bookmarks the virtual address.
Server.Transfer doesn't retrieve from the cache because it isn't executing a pull from the browser -- it's just taking the current page context and transferring execution to a new object, namely the target page.
travisb
Member
485 Points
97 Posts
Server.Transfer does not retrieve cache
Aug 21, 2003 10:58 PM|LINK
mikepope
Contributor
5803 Points
1155 Posts
Microsoft
Re: Server.Transfer does not retrieve cache
Aug 22, 2003 01:47 AM|LINK
travisb
Member
485 Points
97 Posts
Re: Server.Transfer does not retrieve cache
Aug 22, 2003 02:45 PM|LINK
mikepope
Contributor
5803 Points
1155 Posts
Microsoft
Re: Server.Transfer does not retrieve cache
Aug 22, 2003 05:33 PM|LINK