How to solve the problem of using @ PathVariable to pass parameter error 404

This article is about how to solve the problem of using @ PathVariable to pass parameter error 404. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Catalogue

@ PathVariable pass parameter error 404

Pass parameters in restFul style, with slashes in the parameters / problem

@ PathVariable pass parameter error 404

Code:

@ RequestMapping ("/ test1/ {a} / {b}") public String test1 (@ PathVariable int a, @ PathVariable int b, Model model) {int res=a+b; model.addAttribute ("msg", res); return "test";}

Error report:

Cause of error: a "/" is missing from the prefix in the view parser configuration.

Correct:

Pass parameters in restFul style, with slashes in the parameters / problem

Today, I encountered a restful interface path parameter transfer problem, my interface path with a slash, so it is inconsistent with the restful address reported 404 error, and then see such a solution, self-test is available.

@ GetMapping ("user/find/by/ {name} / * *") public String getMapping (@ PathVariable String name, HttpServletRequest request) {String path = request.getAttribute (HandlerMapping.PATH_WITHIN_HANDLER_MAPPING_ATTRIBUTE). ToString (); String path3 = request.getAttribute (HandlerMapping.BEST_MATCHING_PATTERN_ATTRIBUTE). ToString (); String args = new AntPathMatcher (). ExtractPathWithinPattern (path3, path); return name + "/" + args;} Thank you for reading! This is the end of this article on "how to solve the problem of using @ PathVariable to pass parameter error 404". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!