Back button causes current page postback. ASP.Net MVC

Question

I have a controller with 'Details' action and 'Edit' action. I navigate to Edit using View(); then a page with a partial view is rendered.

In the partial view there is a form:

@using (Html.BeginForm("CreateOrEdit", "Licenses", FormMethod.Post, new { @class = "pure-form pure-form-aligned", id = "change", onsubmit = "process(this);" }))
{
    @Html.AntiForgeryToken()
    @Html.ValidationSummary(true)

    <div class="floatLeft width100per">
        @Html.HiddenFor(model => model.Id)
        @Html.HiddenFor(model => model.CustomerId)

        <button onclick="goBack()" type="button" class="pure-button pure-button-primary newButton">Back</button>
        <input type="submit" value="Save" class="pure-button pure-button-primary newButton marginRight10" onclick="getModules(); setGuid('@Guid.NewGuid()');" />
        <div class="floatLeft pure-form">

goBack() function:

function goBack() {
    history.go(-1);
}

If I navigate to Edit and press the back button, everything's fine. But if I press the Save button, form is being submitted and CreateAndEdit action is called - still OK.

The CreateAndEdit action uses:

RedirectToAction("Details", new { id = license.Id });

in order to navigate to Details page again.

Then, if I go to "Edit" again and then press Back - CreateAndEdit action is called again - Not OK!

How can I always go back to "Details" page without calling CreateAndEdit when Back is pressed.

Define as anchor ( <a ) to go to defined url route instead of replying to browser history. — user1672994
– user1672994, Commented May 3, 2018 at 8:31
@ldanLevi You can try to use Ajax call as shown on Can't call function using ajax and inform me if it is working for you. — Murat Yıldız
– Murat Yıldız, Commented May 3, 2018 at 9:08
@MuratYıldız It can work, but it's not the same as going back.. — Idan Levi
– Idan Levi, Commented May 6, 2018 at 6:51

Mark Fitzpatrick · Accepted Answer · 2018-05-03 11:29:07Z

2

You need to disable the cache for the page you don't want a user to be able to go back to due to form submission, etc.

You could try decorating the route with

[OutputCache(NoStore=true, Duration=0)]

I believe [NoCache] will also work as a decoration on your controller action.

answered May 3, 2018 at 11:29

Mark Fitzpatrick

1,6341 gold badge11 silver badges8 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Georg Patscheider · Accepted Answer · 2018-05-03 08:31:50Z

1

I think the behavior you are seeing is standard browser behavior. After you have submitted a form, if you then press the "Back" button of the browser (which is the same as history.go(-1);), the form will be resubmitted.

As a workaround, if the "CreateOrEdit" page is only accessible from the "Details" page, just redirect to the "Details" page directly instead of going through the browser history.

function goBack() {
    location.href = '@Html.Raw(Url.Action("Details", "Licenses",  new { id = Model.License.Id }))';
}

answered May 3, 2018 at 8:31

Georg Patscheider

9,4911 gold badge28 silver badges37 bronze badges

1 Comment

Idan Levi Over a year ago

Thanks, I thought of it too.. But I'm looking for another solution in order to maintain the history as it is.

Collectives™ on Stack Overflow

Back button causes current page postback. ASP.Net MVC

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related