jfinkels

This should be fixable if we require Flask 1.0, since mitsuhiko/flask#503 has been fixed, i.e. we can use blueprint-local error-handling to create an error-handler for HTTP 405 responses that responds...

The versioning for Flask became weird; pallets/flask#503 seems to have been included in Flask 0.11.

See also https://www.rfc-editor.org/rfc/rfc6585.txt

I think this, like #190, is out-of-scope for Flask-Restless. It can be implemented by using, for example, [Flask-Limiter](http://flask-limiter.readthedocs.org/en/stable/), specifically by placing the decorator provided by that package around the view...

I think this, like #190, is out-of-scope for Flask-Restless. It can be implemented by using, for example, [Flask-Limiter](http://flask-limiter.readthedocs.org/en/stable/), specifically by placing the decorator provided by that package around the view...

Would this be solved by issue #497?

I can't think of a good way to use Flask-HTTPAuth, for example, without allowing user-specified decorators on view methods, as described in issue #497, but I haven't personally tried.

Thanks @4311021x. So if `ProcessingException` were modified with an `additional_headers` field, say, and Flask-Restless appended those headers to the response, would that be one way of solving this problem?

You are asking about the most recent stable version, 0.17.0, I believe. Unfortunately, I have made a major rewrite of the project to support JSON API, so I won't be...

No, sorry. I'm afraid I don't have time for it. On Sat, Mar 28, 2020 at 6:29 PM Stephen Holsapple wrote: > @jfinkels are you still maintaining this > library?...