Tryton - Issues

 

Issue7565

Title Use HTTP status when calling unallowed RPC
Priority feature Status resolved
Superseder Nosy List ced, reviewbot, roundup-bot
Type feature request Components sao, tryton, trytond
Assigned To ced Keywords review
Reviews 49511002, 46601002, 70281002
View: 49511002, 46601002, 70281002

Created on 2018-07-06.17:42:25 by ced, last changed by roundup-bot.

Messages
New changeset 1fde41fa524e by Cédric Krier in branch 'default':
Update to new HTTP status code
https://hg.tryton.org/tryton/rev/1fde41fa524e
New changeset b722f0599add by Cédric Krier in branch 'default':
Update to new HTTP status code
https://hg.tryton.org/sao/rev/b722f0599add
New changeset 3aaf4b2ac460 by Cédric Krier in branch 'default':
Use HTTP status code
https://hg.tryton.org/trytond/rev/3aaf4b2ac460
New review70281002 at https://codereview.tryton.org/70281002/#ps1
New review46601002 at https://codereview.tryton.org/46601002/#ps1
New review49511002 at https://codereview.tryton.org/49511002/#ps1
msg42090 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-07-06.17:42:24
We raise a UserError which an untranslated text. But this is a programming error, the client user should never get this error. Also at this point we can not get the message translated.
So for me, it is better to use HTTP status error.
History
Date User Action Args
2018-07-16 14:48:47roundup-botsetmessages: + msg42172
2018-07-16 14:48:02roundup-botsetmessages: + msg42171
2018-07-16 14:47:23roundup-botsetstatus: in-progress -> resolved
nosy: + roundup-bot
messages: + msg42170
2018-07-06 17:51:44reviewbotsetmessages: + msg42096
2018-07-06 17:51:43reviewbotsetreviews: 49511002, 46601002 -> 49511002, 46601002, 70281002
2018-07-06 17:51:25reviewbotsetmessages: + msg42095
2018-07-06 17:51:24reviewbotsetreviews: 49511002 -> 49511002, 46601002
2018-07-06 17:51:03reviewbotsetnosy: + reviewbot
messages: + msg42094
2018-07-06 17:51:02reviewbotsetreviews: 49511002
keyword: + review
2018-07-06 17:42:25cedcreate

Showing 10 items. Show all history (warning: this could be VERY long)