【发布时间】:2014-07-19 05:20:08
【问题描述】:
我有一个配置了一些 CORS 选项的 Flask-Restful API:
api = Api()
api.decorators=[cors.crossdomain(origin='*', headers=['accept', 'Content-Type'])]
...
api.init_app(app)
我的 API 接受 POST 请求,如果请求中的数据无效,可能会失败:
class myAPI(Resource):
def post(self):
args = request.get_json()
if args.get('something'):
return {'message': 'Request worked, data received!',
'something': args['something']}
else:
abort(500, "Error: Data must contain a 'something' field!")
当我成功地向我的 API 发出 POST 请求时,我可以看到 CORS 选项设置正确:
...
* upload completely sent off: 81 out of 81 bytes
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Content-Type: application/json
< Content-Length: 205
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: HEAD, GET, POST, OPTIONS
< Access-Control-Max-Age: 21600
< Access-Control-Allow-Headers: ACCEPT, CONTENT-TYPE
< Server: Werkzeug/0.9.4 Python/2.7.6
但是,如果我的类中的 post 调用通过 abort 方法退出(通过故意向请求发送错误数据),则响应中缺少 Access-Control-* 字段:
* upload completely sent off: 75 out of 75 bytes
* HTTP 1.0, assume close after body
< HTTP/1.0 500 INTERNAL SERVER ERROR
< Content-Type: application/json
< Content-Length: 51
< Server: Werkzeug/0.9.4 Python/2.7.6
是否可以让abort 方法与我的 CORS 规则配合得很好,或者我应该创建自己的完整响应并避免使用中止功能?
【问题讨论】:
标签: python rest flask cors abort