#bvk03_api
warm haloBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1329694179810611220
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
drowsy copper
hello! Stripe accepts form-encoded request bodies, returns JSON-encoded responses as mentioned in https://docs.stripe.com/api
scarlet dome
We are sending 'content-type':'application/x-www-form-urlencoded' in all request and it has working successfully but from today 5:07am ist we are getting below error
"wsp_451_illegal_request_content_type"
Can you please let me know why suddenly this thing is not working by today ?
drowsy copper
Can you share an example code snippet of how you're making a request?
drowsy copper
This is not the code snippet, the screenshot you shared is just the response from the server or your internal logs
scarlet dome
drowsy copper
This error message wsp_451_illegal_request_content_type isn't returned by Stripe. I'll recommend that you check the raw response headers to see where the error message is coming from as a first troubleshooting step
If the request has reached Stripe, there will be a request id : https://docs.stripe.com/api/request_ids
scarlet dome
Is there any possibility of changes from your side in apigateway, load balancer or anything which is proxying api request?
I'm asking because we were sending this header since last two years whithout any problem and today suddenly started getting this error. Once we removed the content-type header completely, everything started working again...
