Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Forcing Post Back

Status
Not open for further replies.
If you're doing it server-side, it's best to use Server.Transfer (if you don't care about the proper URL getting displayed in the browser) which has a significant performance advantage. If you're forcing a refresh on the client, it would be done with expiration headers.

Out of curiosity, what can one buy from your store in the Baptism department?
 
thanks BB,
I would need to pass all the parameters of the URL when posting back because the parameters are used for displaying the layout, department, etc . .
Does the Server.Transfer pass the parameters? How do I use it? Do I just put Server.Transfer by itself?

I tried "Response.Redirect(Request.RawUrl)" and it works, but I don't know what it means and can't find documentation on it.

The Baptism department is for a Web site that I am rebuilding using ASP.NET. It currently looks like this:

I have a page that has the new design I made. None of the Links work yet. This is only for Display purposes:
 
That's not Baptism, that's sprinkling!

...I kid, I kid!

Anyway, Server.Transfer works exactly like Response.Redirect, except there's less back and forth communication between the client and server.

In other words, you'd just use:

Server.Transfer( "/somefolder/blah.aspx?querystring=9" )

or in your case if you want to use Request.RawUrl:

Server.Transfer( Request.RawUrl );
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top