Home/ Questions/Q 7368453
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T03:40:39+00:00

I have 2 asp.net web forms. The first has a ScriptManager, History, UpdatePanel and

  • 0

I have 2 asp.net web forms. The first has a ScriptManager, History, UpdatePanel and GridView; the later is ScriptManager, UpdatePanel and TextBoxes. The premise here is a list that links to a detail form where an item can be edited.

From within the GridView (inside the UpdatePanel), if I use a HyperLink control with the url set to the edit page (with the necessary parameters), change something, save it and then click the back button I see the original list with no updates. Pressing F5 to refresh shows the changes.

If instead I use a LinkButton inside the GridView, and handle that LinkButton in code-behind to perform a Response.Redirect to the same edit page (with the same parameters), make the same changes, save and then click the back button, the list on the original page refreshes automatically to show my changes.

Note that the code in the detail page where the editing/saving takes place does not change – only the way it is first displayed is changed.

My question is this: what is it about the Response.Redirect that causes the page to be refreshed when the back button is clicked, and it it possible to replicate this for the direct HyperLink approach? I would prefer to use the HyperLink method as I see no reason for the postback, but I want the GridView to refresh when the user browses back to it.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A LinkButton causes a postback, the response to which is a HTTP 302 redirect command triggered on the server side by your Response.Redirect. Your web browser therefore does not cache the old version of the page.

    The Hyperlink control simply renders a regular <a> tag which takes you to the detail page on the client side. The browser has no reason to believe the page may have changed, so it presents the cached version when you hit the back button.

    If you want to tell the browser specifically not to cache the page if the back button is used,
    use the cache-control HTTP header. W3C Link,

    In any case, you should provide a link on the detail page (or automatic redirect on accepting changes) which takes the user back to the GridView/summary page, so they don’t have to resort to using the back button.

    Edit:

    Sorry, the previously provided header example was not for Asp.net, but basically you’ll want to do something like this:

    Response.AppendHeader("Cache-Control", "no-cache")
    • 0