Project transformation, there is no interface document at the back end, so you can only look at the interface to write, but the parameters do not know what format to use, whether it is a simple object, FormData, or json, and so on. Can you see it through the browser?
form-dataobjectjson~
json:
object
form
json
query string parameters : is submitted by carrying parameters in the URL. This is the parameter of $_ GET in pgp. (GET)
multipart/form-data : when uploading files using a form, you must make the enctype of the < form > form equal to multipart/form-data. This object is created through the (POST) created by the form
application/x-www-form-urlencoded : native < form > form. If the enctype property is not set, the data will eventually be submitted as application/x-www-form-urlencoded (POST)
application/json : used to tell the server that the message body is a serialized JSON string. Due to the popularity of the JSON specification, all major browsers except the lower version of IE natively support JSON.stringify, server language and have functions to deal with JSON, so there will be no trouble using JSON. (POST)
text/xml : this is ignored. You usually don't encounter it. (POST)
request content-type
as shown in figure in debugging embedded iframe pages, iframe.js is not its own file (probably some security check files for chrome), and then always jumps to this breakpoint, even if I haven t hit the breakpoint, the breakpoint will be removed or...
CSP error in popup: how to solve it? ...
the problem encountered when debugging, the data on the page is normal, but the data is garbled in the debugging tool, what is the problem? : ...
when template syntax is encountered in return, chrome cannot recognize the following content in debugger consoledebuggerchrome babel ...