W3C home > Mailing lists > Public > public-html@w3.org > February 2013

[Bug11458] Managing redirects

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Fri, 1 Feb 2013 00:04:25 +0000
To: "dennisa@pachou.biz" <dennisa@pachou.biz>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B3853BC54E4@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
Bug 11458<https://www.w3.org/Bugs/Public/show_bug.cgi?id=11458>, suggests creating a mechanism to redirect the browser to an alternate URL when the user refreshes the page.

This feature would appear to solve the problem we often see where the browser prompts the user with a "do you want to re-send your information to this page" (because the page may have been a form post result page) by instructing the browser to navigate to another URL instead of refreshing the page.

In the discussion in the bug, it is suggested that history.pushState is a solution to this problem. I haven't thought too deeply about this, but it seems like the History API could be use used to programmatically redirect the page on a "popstate" event.

Does anyone disagree? Am I understanding the proposed solution and/or problem correctly?
Received on Friday, 1 February 2013 00:05:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:36 UTC