Upgrade of Werkzeug from 2.2.3 to 2.3.0 resulting in api failure #2887
Unanswered
BhawnaGoel13
asked this question in
Q&A
Replies: 1 comment
-
|
Hi Team , Would need your inputs here. Is this a known issue or expected behavior ? DO we need to change code accordingly ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Upgrade of Werkzeug from 2.2.3 to 2.3.0 resulting in api failure
As pat of our product we were using Werkzueg version 2.2.3 all the api requests were working fine. But, once we tried to upgrade it to any of the version above it. All the api's started failing with the below response and 500 error code.
<title>500 - Request did not return bytes</title>Is there any known issue or any fix that we can apply in order to fix this issue.
It should have returned 200 OK as a response
Environment:
Beta Was this translation helpful? Give feedback.
All reactions