Up to now, I have gone through two internships , Also because I like surfing the Internet , I know many friends from big factories . Anyway, everyone's consensus is Restful The benefits outweigh the disadvantages . I checked the information for a few days , To sum up a little

Why not Restful

1. Browser aspect

• Browsers are generally right GET and POST The best support for
• Browser form form Submission only supports GET and POST

2.SpringMVC aspect

• SpringMVC analysis POST The request can be parsed automatically param and body, No comments needed , and PUT DELETE Request must be added @RequestParam、@PathVariable、@RequestBody annotation , although Spring3 Support for PUT Mapping of request body , But it needs to be in web.xml perhaps WebMvcConfigurerAdapter To configure ———————— This is really useful , I have maintained this project for a long time and feel it is really convenient , Many fields that do not need to be matched can be written directly

3. Business aspect

• One “ Delete ”“ Change ” The operation may not be so clean , There may be a lot of “ check ”“ increase ” operation , But with one PUT Even basic RESTful Our advantages have become disadvantages
• The different operations of adding, deleting, modifying and querying can be done through url To distinguish ： for example */deleteXxxx or editXxxx

4.Http In terms of agreement

• meanwhile ,POST Requests are submitted twice by default in most browsers tcp package , It's safer when the network environment is poor
• PUT and DELETE stay http The essence of the agreement and POST equally , There is no advantage , Instead, the SpringMVC Some problems are easy to appear in

When can I use Restful

If and only if

• Idempotent modification delete It can be used put,delete; Not idempotent post
• Deleting is deleting , Modification is modification , It will not affect other business data
• Training institutions deceive xiaobaishi

Get and Post Some of the differences

• “ Whether to submit a large amount of data ” The function of can be directly determined by POST and GET To distinguish between ,GET Can't put body Parameters , Data can only be exposed in url On , But browsers url The length of is mostly limited to 2kb, It can be used POST Let's play it body Parameters .
• GET The requested request data may be cached by the browser
• If the request is not idempotent, use GET, If the result is cached, an error will occur , By request Parameters with timestamp, etc. do not repeat irrelevant parameters To enforce cache prevention
• If sensitive information is used GET, Then your sensitive information may be completely saved in the local browser . Of course , It can be solved by encryption