Home  >  Article  >  Web Front-end  >  What is the difference between history and hash in vue

What is the difference between history and hash in vue

WBOY
WBOYOriginal
2022-03-17 15:48:2624667browse

Difference: 1. The hash route has "#" on the URL in the address bar, but the history route does not; 2. When performing a press enter refresh operation, the hash route will be loaded into the page corresponding to the address bar, while the history route Generally, a 404 error will occur; 3. Hash supports some lower version browsers, but history does not support it.

What is the difference between history and hash in vue

The operating environment of this article: Windows 10 system, Vue version 2.9.6, DELL G3 computer.

What is the difference between history and hash in vue

  • 1. The hash route has # on the address bar URL and is read with window.location.hash. The history route will not look better.

  • 2. We perform a press enter refresh operation, and the hash route will be loaded to the page corresponding to the address bar, while the history route usually reports a 404 error (refresh is Network request, an error will be reported if there is no backend preparation).

  • 3. Hash routing supports lower version browsers, while history routing is a new API in HTML5.

  • 4.hash is characterized by that although it appears in the URL, it is not included in the http request, so it has no impact on the backend, so changing the hash will not re- Load the page, so this is also a must for single-page applications.

  • 5.history uses the browser's history stack. There were back, forward, and go methods before. Later, pushState() and replaceState() methods were added in HTML5. They Provides the function of modifying the history record. However, when modifying, although the current URL is changed, the browser will not immediately send a request to the backend.

  • 6. This mode of history requires background configuration support. For example: when we go to the homepage of the project, everything is normal and can be accessed, but when we refresh the page or directly access the path, 404 will be returned. That is because in history mode, window.history is only dynamically operated through js. To change the path in the browser address bar, no http request is initiated, but when I enter this address directly in the browser, I must initiate an http request to the server, but this target does not exist on the server, so Will return 404

Summary

Of course, history is not good for everything. Although SPA works well in the browser, the difference between the two comes when you really need to initiate an HTTP request to the backend through the URL. Especially when the user manually enters the URL and presses Enter, or refreshes (restarts) the browser.

1: In hash mode, only the content before the hash symbol will be included in the request, such as http://www.abc.com, so for the backend, even if the routing is not implemented Full coverage, no 404 error will be returned.

2: In history mode, the URL of the front-end must be consistent with the URL that actually initiates the request to the back-end. Such as http://www.abc.com/book/id. If the backend lacks routing processing for /book/id, a 404 error will be returned

Problem solution:

Solutions to 404 errors: Many methods introduced online will not work. Install the URL rewriting module, configure the rewriting rules, and point them to index.html. Or directly place the web.config file generated by URL rewriting directly in the root directory of the website.

【Related recommendation: "vue.js Tutorial"】

The above is the detailed content of What is the difference between history and hash in vue. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn