Search code examples
asp.netresponse.redirectpostbackurl

Is there a performance difference between postbackurl and response.redirect?


i've just created a page that needs to update that contains multiple documents. Each document can be selected from a menu on the page.

I would normally wrap this up in a multiview + update panel, however I needed to update the url as well to reflect the document selected.

At the moment I've done this using a different postbackurl (so no update panel), however this means displaying a nasty "Firefox needs to resend...2 message when the back button is clicked.

I could, instead redirect from the button event. This would have the same effect, but without the message.

The question I have is does the postbackurl method offer any significant advantages over the redirect. By advantages I mean performance.

Any thoughts would be appreciated.


Solution

  • Let us consider the two cases :

    • no postbackurl, with redirect : the client submit the form, the server issues a redirect, the client issues a get request to the final url and gets the content

    • postbackurl : the client submits the form to the postbackurl and gets the content

      Second case is better in terms of performance ( no network roundtrip to get and follow the redirect )

    But redirect has some advantages in the fact that a get request is issued. (no reload or repost problem)

    Anyway, I was wondering why you couldn't just use HyperLink with NavigateUrl to get to your content.