Just looking at those requests again;
x-www-url-encoded body
Request Headers
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth *****
Cache-Control: no-cache
Postman-Token: 93a600c0-68e9-48fe-9d8d-faa34283043f
Host: upload.twitter.com
Content-Length: 141
Cookie: guest_id=v1%3A171399458995171879; lang=en
Request Body
media: “iVBORw0KGgoAAAANSUhEUgAAAAgAAAAIAQMAAAD+wSzIAAAABlBMVEX///+/v7+jQ3Y5AAAADklEQVQI12P4AIX8EAgALgAD/aNpbtEAAAAASUVORK5CYII”
Raw Body
Request Headers
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth ****
Cache-Control: no-cache
Postman-Token: 8c1d7593-a36f-40f1-b175-27322ad09102
Host: upload.twitter.com
Content-Length: 128
Cookie: guest_id=v1%3A171399458995171879; lang=en
Request Body
media: “iVBORw0KGgoAAAANSUhEUgAAAAgAAAAIAQMAAAD+wSzIAAAABlBMVEX///+/v7+jQ3Y5AAAADklEQVQI12P4AIX8EAgALgAD/aNpbtEAAAAASUVORK5CYII”
The key difference being the content length. The string is 128, so why does the x-www-form-urlencoded body submit a string of 141.
If i manually set a Content-Length as anything higher than 128 on my raw body request, it hangs and never completes a transaction. If i set it 128 or lower it fails in the same way as previously
What is the difference in how that is calculated compare to the raw body with a Content-Type: x-www-form-urlencoded