gogoWebsite

1. Request path

A correct request path should be fromResource path + resource namecomposition

http://localhost:8080/sk_war_exploded/ is the absolute path

http://localhost:8080/sk_war_exploded is the resource path 

As the resource name

Relative path：/ is a relative path. The relative path will depend on another path as the reference path, and combine it with this reference path to locate a resource.

Absolute path =Reference path + relative path

2. Whether to add a slash (/) in front of the relative path will produce different effects

2.1. The path is resolved in the foreground, so the root path ishttp://localhost:8080/(Root path of the server)

1. Relative path without slashes at the beginning

<a href="" th:if="${}==null" th:value="wsk">Login</a>

When the relative path does not have a slash, this path isCurrent resource pathA subpath of 

The access address at this time is:

http://localhost:8080/sk_war_exploded/, you can access it correctly at this time

2. Relative path with slashes at the beginning

<a href="/" th:if="${}==null">Register</a>

 When the relative path has a slash, this path means that the path isRoot pathA subpath of
The access address at this time is:

http://localhost:8080/Resolving address failed

2.2. The path is resolved in the background, so the root path ishttp://localhost:8080/sk_war_exploded/ 

1. Relative path without slashes at the beginning

//@RequestMapping with / is an absolute path, adding a slash is to find the following path, and not to include it (the specification should be included)
     @RequestMapping(value = "", method = )
     public String login(HttpServletRequest request, Model model) {
 
     }

When the relative path does not have a slash, this means that the path isCurrent resource pathA subpath of

The access address at this time is:

http://localhost:8080/sk_war_exploded/, you can access it correctly at this time

2. Relative path with slashes at the beginning

//@RequestMapping with / is an absolute path, adding a slash is to find the following path, and not to include it (the specification should be included)
     @RequestMapping(value = "/", method = )
     public String login(HttpServletRequest request, Model model) {

  }

When the relative path has a slash, the opening path means that the path isRoot pathA subpath of
The access address at this time is:

http://localhost:8080/sk_war_exploded/, you can access it correctly at this time

reason:
Since when the background parses the path, the root path ishttp://localhost:8080/sk_war_exploded/，
1. When we do not add slashes, we parse them with relative paths, but because our root path is http://localhost:8080/sk_war_exploded/, the final positioning is still back to http://localhost:8080/sk_war_exploded/,
2. When adding a slash, it is parsed with an absolute path, but since the root path and the current resource path are both located at http://localhost:8080/sk_war_exploded/, the final positioning is still returned to http://localhost:8080/sk_war_exploded/, but,The specification stipulates that slashes (/) should be added