Need to navigate users to landing page when browser back button is pressed

Question

I have a ASP.net MVC web application which consists of several pages. The requirement is like this:

when users are using the application, suppose user is in page 7, suddenly user navigates away from the application by typing a external internet URL say Google.com.

Now when user presses the back button of the browser, Instead of bringing him back to page 7, we need to redirect him to Page 0 which is the landing page of the application.

Is there any way to achieve this? we have a base controller which gets executed every time a page loads as well as a master page (aspx). Can we do something there so that this behavior can be implemented in all the pages?

Ilya Sulimanov · Answer 1 · 2013-12-05T13:05:53.750

0

I can offer the following idea:

When user press <a href='external url' onclick='clearHistory'>link</a> You can save in browser history of the desired url:

<script>  
function clearHistory()
{
  var reternUrl = getReternUrl(); 
  History.pushState({}, null, reternUrl);
}
</script>

more about history.js

Edit: ok, then handle beforeunload event:

   $(window).on('beforeunload', function () {
                     var reternUrl = getReternUrl(); 
                     History.pushState({}, null, reternUrl);
                });

edited Dec 05 '13 at 13:05

answered Dec 05 '13 at 10:15

Ilya Sulimanov

7,636
6
47
68

BUt if user clicks a bookmark or types the external URL in the browser address bar then I wont be able to clear history :-/ – Manas Saha Dec 05 '13 at 11:09

score 0 · Answer 2 · edited May 23 '17 at 10:25

EDIT: Shortened and slightly changed code to better answer exact question (based on first comment to this answer)

Addition to answer above about editing the browser history for the case where the user types the external URL in the browser address bar.

You could try to detect url change as posted in How to detect URL change in JavaScript. Example of this using jquery (taken and edited slightlyfrom post linked to above):

For newer browsers:

$(window).bind('hashchange', function() {
    /* edit browser history */
});

For older browsers: function callback(){ /* edit browser history */ }

function hashHandler(callback){
    this.oldHash = window.location.hash;
    this.Check;

    var that = this;
    var detect = function(){
        if(that.oldHash!=window.location.hash){
            callback("HASH CHANGED - new hash" + window.location.hash);
            that.oldHash = window.location.hash;
        }
    };
    this.Check = setInterval(function(){ detect() }, 100);
}

hashHandler(callback); //start detecting (callback will be called when a change is detected)

I'll get back to you on bookmarks (still need to check that out).

Thanks, for the time being I am only concerned if the user opens a external page in the same browsing window as the application. — Manas Saha, Dec 05 '13 at 11:10

score 0 · Answer 3 · answered Dec 05 '13 at 10:21

I think the best solution is to use iframe and switch between your steps inside of iframe. It would be quite easy to do, because you don't need to redesign your application. Anytime when user tries to switch to other url and come back, the iframe will be loaded again from the first step.

Be sure to disable caching on every step of your application. You can do this by applying NoCache attribute to your controller's actions:

public class NoCache : ActionFilterAttribute
{
    public override void OnResultExecuting(ResultExecutingContext filterContext)
    {
        filterContext.HttpContext.Response.Cache.SetExpires(DateTime.UtcNow.AddDays(-1));
        filterContext.HttpContext.Response.Cache.SetValidUntilExpires(false);
        filterContext.HttpContext.Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
        filterContext.HttpContext.Response.Cache.SetCacheability(HttpCacheability.NoCache);
        filterContext.HttpContext.Response.Cache.SetNoStore();

        base.OnResultExecuting(filterContext);
    }
}

score 0 · Answer 4 · answered Dec 05 '13 at 10:29

There is 2 case over here

First is browser in online mode, in this case you have to store your last page get request in session, if user hit back button it will re initiate get request for that page again you can trap it and send them to landing page, You have to take care that get request for page happen only once other action must be post.

Second is browser in offline mode, in this case you have to take care that your response should not put any cache foot print in browser, there are many code example you can found on net for this purpose.

Need to navigate users to landing page when browser back button is pressed

4 Answers4