Site has a certain amount of traffic, you need to find ways to improve the stickiness of the site, the world's buyers recently intend to get a group of foreign trade tools, is a number of commonly used tools, such as the World Time query http://www.buyerinfo.biz/tools/global-time/, Hscode inquiries, exchange rate inquiries and conversion, and so on, a few have been completed, we look at a little more to mention the views. Which also has JS refresh, not very will get, so record,
Reload method that forces the browser to refresh the current page.
Syntax: Location.reload ([Bforceget])
Parameters: Bforceget, optional parameter, default to False, take the current page from the client cache. True to get the latest page from the service, equivalent to the client-click F5 ("Refresh")
Replace method, which replaces the item currently cached in history (the client) by specifying a URL, so after you use the Replace method, you cannot access the URL that has been replaced by "forward" and "back".
Syntax: Location.replace (URL)
In practical applications, when refreshing the page, we usually use: Location.reload () or History.go (0). Because this practice is like the client point F5 Refresh the page, so the page method= "POST", will appear "page expiration" hint. That's because the session's security protection mechanism. It can be thought that when the Location.reload () method is invoked, the ASPX page already exists in the server memory, so it must be IsPostback. If this applies: we need to reload the page, which means we expect the page to be recreated on the server side, and we expect it to be not IsPostback. Here, Location.replace () can complete this task. The replaced pages are regenerated each time on the server side.
Can write this: Location.replace (LOCATION.HREF);