I have an endpoint that receives “content-type” of “application/json” but when I hit it from javascript, it returns a 415 unsupported media type status code. But When I use postman it works. So I inspected the network tab of dev tools and discovered the request headers content type is text/plain instead of the application/json I set it to be. Why is this happening ?

chukwuebuka65:
I have an endpoint that receives “content-type” of “application/json” but when I hit it from javascript, it returns a 415 unsupported media type status code. But When I use postman it works. So I inspected the network tab of dev tools and discovered the request headers content type is text/plain instead of the application/json I set it to be. Why is this happening ?

This is why ChatGpt was created

Paystack:


This is why ChatGpt was created

In as much as chatgpt is useful, its still not a human being. I actually got the answer i am looking for on stackoverflow as chatgpt couldnt help me.

chukwuebuka65:


In as much as chatgpt is useful, its still not a human being. I actually got the answer i am looking for on stackoverflow as chatgpt couldnt help me.

It provides better help and faster help than humans as at now.

chukwuebuka65:
I have an endpoint that receives “content-type” of “application/json” but when I hit it from javascript, it returns a 415 unsupported media type status code. But When I use postman it works. So I inspected the network tab of dev tools and discovered the request headers content type is text/plain instead of the application/json I set it to be. Why is this happening ?

Your path to the file is wrong. Target your files properly.

chukwuebuka65:
I have an endpoint that receives “content-type” of “application/json” but when I hit it from javascript, it returns a 415 unsupported media type status code. But When I use postman it works. So I inspected the network tab of dev tools and discovered the request headers content type is text/plain instead of the application/json I set it to be. Why is this happening ?

Set the content-type in JS. It’s most likely never the browser

stanliwise:

Set the content-type in JS. It’s most likely never the browser

OP, this is the answer you are lookin for here. Set the content type in your headers before sending the request

Luckydonalds:

OP, this is the answer you are lookin for here. Set the content type in your headers before sending the request

I have found the solution.

stanliwise:

Set the content-type in JS. It’s most likely never the browser

I have found the solution.

chukwuebuka65:


I have found the solution.

You can as well talk about the solution just so someone stumble on this thread in future

stanliwise:

You can as well talk about the solution just so someone stumble on this thread in future

You're wise

stanliwise:

You can as well talk about the solution just so someone stumble on this thread in future

It has to do with cors. I was getting cors error, so I added “no cors” to the fetch mode configuration to bypass the error . But with that configuration, the browser does not allow any other value for the “content-type” header expect “text/plain”. So I contacted the backend team and we were able to rectify it.