By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,602 Members | 1,507 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,602 IT Pros & Developers. It's quick & easy.

Problem with Server.Transfer

P: n/a
I have an app that uses Server.Transfer from page1 to page2. page2 needs to be able to read all the values from page1's form. The problem is, if the user clicks the back button on page2 after a Server.Transfer, the user gets a page has expired error.

Is there a way to keep using Server.Transfer, but also have the back button work normally?
Nov 18 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Although I have not used Transfer very much, I would imagine not. The
reason being that the back button is controlled by the browser and when you
call Transfer, the browser does not know that you are changing pages, all
the work is done on the server. So, as far as the browser is concerned, you
are still on page1, regardless of how many calls to Transfer you make.

Someone can correct me if I am wrong. Would not be the first time. :p

"john" <an*******@discussions.microsoft.com> wrote in message
news:89**********************************@microsof t.com...
I have an app that uses Server.Transfer from page1 to page2. page2 needs to be able to read all the values from page1's form. The problem is, if the
user clicks the back button on page2 after a Server.Transfer, the user gets
a page has expired error.
Is there a way to keep using Server.Transfer, but also have the back

button work normally?
Nov 18 '05 #2

P: n/a
Selecting history buttons just pull dead pages from cache, they do not
request new page from server so no code runs.

Charlie
"john" <an*******@discussions.microsoft.com> wrote in message
news:89**********************************@microsof t.com...
I have an app that uses Server.Transfer from page1 to page2. page2 needs to be able to read all the values from page1's form. The problem is, if the
user clicks the back button on page2 after a Server.Transfer, the user gets
a page has expired error.
Is there a way to keep using Server.Transfer, but also have the back

button work normally?
Nov 18 '05 #3

P: n/a
I use Server.Transfer extensively in the app I am working on now and I don't
have any problems with the back button. It's hard to say what I'm doing
differently from what you're doing, or vice versa, but that at least shows
that you can use the back button without having to refresh the page.

Peter, you're right about one thing. When the second page is loaded from
Server.Transfer, the browser address bar still shows the first page address
but after posting back via any control or submitting the form, then the
address bar shows the address for the second page.

Hope that helps some, John. At least you know it's possible.

Dale

"Peter Rilling" <pe***@nospam.rilling.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Although I have not used Transfer very much, I would imagine not. The
reason being that the back button is controlled by the browser and when you call Transfer, the browser does not know that you are changing pages, all
the work is done on the server. So, as far as the browser is concerned, you are still on page1, regardless of how many calls to Transfer you make.

Someone can correct me if I am wrong. Would not be the first time. :p

"john" <an*******@discussions.microsoft.com> wrote in message
news:89**********************************@microsof t.com...
I have an app that uses Server.Transfer from page1 to page2. page2
needs to be able to read all the values from page1's form. The problem is, if the user clicks the back button on page2 after a Server.Transfer, the user gets a page has expired error.

Is there a way to keep using Server.Transfer, but also have the back

button work normally?

Nov 18 '05 #4

P: n/a
Charlie@CBFC wrote:
Selecting history buttons just pull dead pages from cache, they do not
request new page from server so no code runs.


Careful... that depends
a) on the browser,
b) on the page's cache settings.

Cheers,

--
Joerg Jooss
jo*********@gmx.net
Nov 18 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.