We deployed Sentry on one of our Flask apps today (via pip3 install raven[flask]), which revealed a bug we'd overlooked. But in trying to replicate the bug via Sentry's suggested curl command, we noticed that the suggested curl command seems to be mistaking POST data submitted as x-www-form-urlencoded for JSON.
Specifically, the suggested curl command in Sentry's web UI (at a URL of the form https://sentry.io/ORG/PROJECT/issues/#/) suggests using
-H "Content-Type: application/x-www-form-urlencoded"
--data "{\"username\":\"\",\"script\":\"foo\",\"cmd\":\"\",\"format\":\"html\"}"
among other command-line args. But the suggested curl command should actually be
-H "Content-Type: application/x-www-form-urlencoded"
--data "cmd=&format=html&username=&script=foo"
(among other command-line args)?
Perhaps related to #5599, but this is perhaps just an issue in the web UI?
We deployed Sentry on one of our Flask apps today (via
pip3 install raven[flask]), which revealed a bug we'd overlooked. But in trying to replicate the bug via Sentry's suggestedcurlcommand, we noticed that the suggestedcurlcommand seems to be mistaking POST data submitted asx-www-form-urlencodedfor JSON.Specifically, the suggested
curlcommand in Sentry's web UI (at a URL of the formhttps://sentry.io/ORG/PROJECT/issues/#/) suggests usingamong other command-line args. But the suggested
curlcommand should actually be(among other command-line args)?
Perhaps related to #5599, but this is perhaps just an issue in the web UI?