For servers that do not support the application/x-www-form-urlencoded for example for APIs which expect the content type to be application/json, the extension is raising the false positive issues because the server would send 400 or something due to incompatible content type but when extension sends request to confirm validity with original content-type or without the content-type header a valid response is returned, which make the extension believe that it has found an issue.