Change url of supplied page without doing a redirect?

[Martin]

I know this might seem like an odd question.

I've got a page that has a few url parameters. There's a couple of modes
the page can be entered in, with correspondingly different urls params.

Once on the page, typically the user causes a post back to occur. I then
want the url to reflect the new mode of the page. Right now I am doing that
with a redirect to the same page, but with different url parameters, however
this is inefficient in terms of request processing.

Really I want to serve up the page in response to the postback event, but to
change the url associated with that page. If this is possible, I guess it's
an http protocol issue.

Anyone?
Thanks
Martin

 

[Martin]

Ah - HTTP Header Content-Location looks promising.

 

[Martin]

Hmm, that didn't have the desired effect. The browser (IE6) still displays
the requested url string.

rfc2616 says:
"The Content-Location value is not a replacement for the original
requested URI; it is only a statement of the location of the resource
corresponding to this particular entity at the time of the request.
Future requests MAY specify the Content-Location URI as the request-
URI if the desire is to identify the source of that particular
entity."

Looks like I'm out of luck unless someone says otherwise......

Martin

 

[moondaddy]

Here's the content of a response I got from making a similar post.





Hi Moondaddy,

From your description, one of your ASP.NET web page will checking a certain
querystring parameter in the requested url and do some session operations
depending on the parameter value. And currently you want to remove the
certain parameter from the request url if it exist in the first request, so
that the following postback request won't do the duplicated operations on
the session ,yes?

As far as I know, the QueryString collection of the Request object are not
modifiable by user, and I think you can consider the following means:
1.Still let the querystring param remain in the url and use the
Page.IsPostBack property to check whether its the first time loaded or post
back request so as to determine whether to do the session modification or
not.

2. User Server.Transfer or response.Redirect to reload the current page
with the non-querystring url. But this will reduce the performance.

Please have a consider on the above things. If you have any other different
ideas, please also feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Martin]

Hi Moondaddy,

Thanks for that. I would use post instead of get, but posting from another
page seems problematic in ASP.Net 1.x. I guess the other option is session
vars, but it really shouldn't have to be. I think cross posting *asp.net*
forms is something that is facilitated in asp.net2.0

What solution are you working with at present?

Martin