Stop raising FormDataRoutingRedirect
See original GitHub issuehttps://github.com/pallets/werkzeug/pull/1342 sets the status code for RequestRedirect
to 308, so the request body (form data) will be preserved. We no longer need to fail with FormDataRoutingRedirect
. @pgjones
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
FormDataRoutingRedirect exception from a URL without ...
My guess is that your /myurl route is not defined to accept POST requests, and your /<a>/ route is, so Werkzeug picks /<a>/...
Read more >Python – FormDataRoutingRedirect exception from a URL without ...
I'm doing an ajax POST request and I'm getting this exception: [Fri Nov 29 20:48:55 2013] [error] [client 192.168.25.100] self.raise_routing_exception(req) ...
Read more >Python raise exception
This page shows Python code examples for raise exception. ... from .debughelpers import FormDataRoutingRedirect raise FormDataRoutingRedirect(request).
Read more >flask.app — coaster 0.7.0 documentation - Read the Docs
Raise exception if an unexpected attr is set, a "controlled" flask.g. ... If you want to run the application in debug mode, but...
Read more >python/1190/ReproWeb/3rdParty/python/flask/debughelpers.py ...
clast DebugFilesKeyError(KeyError, astertionError): """Raised from ... clast FormDataRoutingRedirect(astertionError): """This exception is raised by Flask ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think in debug mode we should still fail. Triggering a slashes-related redirect on form submission likely indicates a bug or bad code (e.g. not using
url_for
)Yeah, go for it! Can’t completely remove it because we’d have to bump the minimum Werkzeug version to 0.15, which hasn’t been released yet. For now it should check if the status code is 307 or 308 and not raise in that case.