You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe it has something to do with the mismatch in the Content-Type and the input. If the Content-Type header is set to application/x-www-form-urlencoded, the response will return a 200, but with the following body:
{
"[object Object]": "",
"id": 1
}
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
Expected response:
Actual response:
I believe it has something to do with the mismatch in the
Content-Type
and the input. If theContent-Type
header is set toapplication/x-www-form-urlencoded
, the response will return a 200, but with the following body:The text was updated successfully, but these errors were encountered: