Demo: http://wfquery.top/demo/07.fo.

• formdata when you use FormData to submit POST request data (you can submit blob data, that is, file upload is supported), the data is submitted in request.plaload

$.ajax({
  type: 'POST',
  url: '/',
  form: $('form')
});

https://github.com/shy2850/wf...

• GETquerystring

• if you use POST to submit querystring, you need to set Content-Type: 'application/x-www-form-urlencoded', data to be submitted through xhr.send (data)

https://github.com/shy2850/wf.

• the above is a more common form data submission method. You can also directly submit json format strings and the like. The server can also directly submit buffer when you get the whole query and go to parseJSON, file upload when the xhr.send (buffer) file is uploaded.

as a matter of fact, whether the "Content-Type" of the request header needs to be set at the front end is entirely determined by the server. Whether the above is in querystring-param or query-json format, it can be submitted in the same location. Therefore, in many cases, we need to set the format interaction specification for the agreement between the front and back end. You can also define the rules yourself without following this convention in the project.

URL is as follows:
scheme://user:password@host:port/path;params?query-sharpfrag

query section is Query String Parameters

HTTP is as follows

<method>  <request-URL>  <version>

<header>

<entity-body>

request payload and form data are the contents of entity-body blocks, but parsing behaviors are distinguished by Content-type .
generally form-data is `Content-type=application/x-www-form-urlencoded
the rest generally defaults to request payload (I don't know if the file is uploaded, but you can search it if you are interested).

Query String Parameters you can bring it regardless of the request method, depending on whether you want to parse it or not.
entity-body requires partial request methods
POST , PUT , PATCH , DELETE , OPTIONS , (UN) LINK , LOCK , PROPFIND , VIEW
and so on.