When using the APIPost for interface testing, some custom or unusual content-Type formats may be used. In this case, you need to manually define the content-Type in the header.

Here we define a custom content-Type in the format application/octet-stream

Then select “form-data” for the body, and then fill in nothing for the body. Click “Send”, and the format of the content-Type is custom application/ OCtet-stream.

Content-type is not passed according to the custom application/octet-stream.

Finally, it was found that apiPost customized content-Type and sent with parameters did not support body as form-data and X-www-form-urlencoded. You can customize the Content-Type and send it with parameters when using body as a json format, for example.