You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing around with django-json-rpc and jsonrpclib. Almost all exceptions in exceptions.py return status 500 which xmlrpclib(that jsonrpclib uses) treats as a serious error and it doesn't parse the response. And most of the errors except OtherError are not really internal server errors and the server responds accurately with an error according to the json rpc spec. So maybe status = 200 is more accurate to known handled exceptions?
The text was updated successfully, but these errors were encountered:
nycholas
added a commit
to nycholas/django-json-rpc
that referenced
this issue
Jul 15, 2012
I've been playing around with django-json-rpc and jsonrpclib. Almost all exceptions in exceptions.py return status 500 which xmlrpclib(that jsonrpclib uses) treats as a serious error and it doesn't parse the response. And most of the errors except OtherError are not really internal server errors and the server responds accurately with an error according to the json rpc spec. So maybe status = 200 is more accurate to known handled exceptions?
The text was updated successfully, but these errors were encountered: