Setting the Content-Type on a cross-origin request can trigger a CORS
preflight request depending on the value being set. Best case it adds
extra latency, worst case, the server either doesn't know how to handle
the request or rejects the request.
Since there is no purpose for a Content-Type without an entity, we can
skip the header.
Setting the Content-Type on a cross-origin request can trigger a CORS preflight request depending on the value being set. Best case it adds extra latency, worst case, the server either doesn't know how to handle the request or rejects the request.
Since there is no purpose for a Content-Type without an entity, we can skip the header.
Issue: #128