Server.Transfer with url change

[David Thielen]

Hi;

I would like to do the equivilent of a Server.Transfer() so I can pass data
along in the context. But I want the new url to show like a
Response.Redirect() - but that loses the data I stuffed in Context.

What I need is a way to a) have the url of the page redirected to show up,
b) pass data to the redirected page, and c) have the passed data go away once
the new page is up. I don't want to use Session because if for some reason it
does not get to the second page, that data is left connected to the Session.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

[bruce barker \(sqlwork.com\)]

the url in the browser winow, is the url of the last request. if you do a
server transfer, all you are doing is calling different backend code to
process the request, not changing the request. there is no way to change the
url in the browser without doing a request to that url (think of the
security problems if you could).

so the only way for the server to change the url in the browser is with a
redirect.

what you shoudl do is tie the data to ticket, and pass the ticket in the url
string in the redirect. the ticket should only be good for one fetch and
should have a timeout. session should be fine for this.
-- bruce (sqlwork.com)

"David Thielen" <th*****@nospam.nospam> wrote in message
news:AD**********************************@microsof t.com...

Hi;

I would like to do the equivilent of a Server.Transfer() so I can pass
data
along in the context. But I want the new url to show like a
Response.Redirect() - but that loses the data I stuffed in Context.

What I need is a way to a) have the url of the page redirected to show up,
b) pass data to the redirected page, and c) have the passed data go away
once
the new page is up. I don't want to use Session because if for some reason
it
does not get to the second page, that data is left connected to the
Session.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

[David Thielen]

perfect - thanks

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

"bruce barker (sqlwork.com)" wrote:

the url in the browser winow, is the url of the last request. if you do a
server transfer, all you are doing is calling different backend code to
process the request, not changing the request. there is no way to change the
url in the browser without doing a request to that url (think of the
security problems if you could).

so the only way for the server to change the url in the browser is with a
redirect.

what you shoudl do is tie the data to ticket, and pass the ticket in the url
string in the redirect. the ticket should only be good for one fetch and
should have a timeout. session should be fine for this.
-- bruce (sqlwork.com)

"David Thielen" <th*****@nospam.nospam> wrote in message
news:AD**********************************@microsof t.com...

Hi;

I would like to do the equivilent of a Server.Transfer() so I can pass
data
along in the context. But I want the new url to show like a
Response.Redirect() - but that loses the data I stuffed in Context.

What I need is a way to a) have the url of the page redirected to show up,
b) pass data to the redirected page, and c) have the passed data go away
once
the new page is up. I don't want to use Session because if for some reason
it
does not get to the second page, that data is left connected to the
Session.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

[Previous Page]

E.g
TextBox txt=(TextBox) PreviousPage.FindControl("txtname");
with this way you can access the data which store previous page.
"David Thielen" wrote:

perfect - thanks

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

"bruce barker (sqlwork.com)" wrote:

the url in the browser winow, is the url of the last request. if you do a
server transfer, all you are doing is calling different backend code to
process the request, not changing the request. there is no way to change the
url in the browser without doing a request to that url (think of the
security problems if you could).

so the only way for the server to change the url in the browser is with a
redirect.

what you shoudl do is tie the data to ticket, and pass the ticket in the url
string in the redirect. the ticket should only be good for one fetch and
should have a timeout. session should be fine for this.
-- bruce (sqlwork.com)

"David Thielen" <th*****@nospam.nospam> wrote in message
news:AD**********************************@microsof t.com...

Hi;

I would like to do the equivilent of a Server.Transfer() so I can pass
data
along in the context. But I want the new url to show like a
Response.Redirect() - but that loses the data I stuffed in Context.

What I need is a way to a) have the url of the page redirected to show up,
b) pass data to the redirected page, and c) have the passed data go away
once
the new page is up. I don't want to use Session because if for some reason
it
does not get to the second page, that data is left connected to the
Session.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com