Use and principle of rest

1. When we Need to use delete and put When sending a request by , You will find that the default way of request is get, We need to configure a hiddenHttpMethodFilter ,springboot It's configured by default , We need to start it manually .

Opening mode , It can also be said to be the way of use

By default post The way , Just in the hidden field _method The latter designation is based on put perhaps delete The way is ok

The last step : stay yml Open... In the configuration file hiddenHttpMethodFilter

spring:
  mvc:
    hiddenmethod:
      filter:
        enabled: true

If we need to modify the default   Hide domain name _method 

Fang fa :  Through one method, it becomes 了   _Z

package com.zwz.springbootweb.config;

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.filter.HiddenHttpMethodFilter;

@Configuration(proxyBeanMethods = false)
public class WebConfig {
    @Bean
    public HiddenHttpMethodFilter hiddenHttpMethodFilter(){
        HiddenHttpMethodFilter hiddenHttpMethodFilter = new HiddenHttpMethodFilter();
        hiddenHttpMethodFilter.setMethodParam("_Z");
        return hiddenHttpMethodFilter;
    }

}

Rest principle :

The form submission will bring _method=PUT, Ask to come and be  HiddenHttpMethodFilter Intercept , Check whether the request is normal , And is POST

Get _method Value ( Compatible with the following requests :PUT.DELETE.PATCH)

Native request（post）, Packaging mode requesWrapper Rewrote getMethod Method , The returned value is the passed in value .

When the filter chain is used wrapper. Future method calls getMethod Is to call requesWrapper

If you are developing on the client such as Android, you don't need to use  HiddenHttpMethodFilter, Direct use of native servelt Drop corresponding method