aboutsummaryrefslogtreecommitdiff
path: root/3rdparty
diff options
context:
space:
mode:
authorKitsune Ral <Kitsune-Ral@users.sf.net>2020-08-04 13:32:57 +0200
committerKitsune Ral <Kitsune-Ral@users.sf.net>2020-08-04 13:51:40 +0200
commit7982e62cf53c830b821cbe2d85fd4fef1e633576 (patch)
tree51c53c78e0178cc6e697ca53ff7818addddc91da /3rdparty
parent68a4875c047611e7f58ed001dc9ec4231a11728a (diff)
downloadlibquotient-7982e62cf53c830b821cbe2d85fd4fef1e633576.tar.gz
libquotient-7982e62cf53c830b821cbe2d85fd4fef1e633576.zip
BaseJob: go for a retry on IncorrectResponse
The most frequent occurence of IncorrectResponse so far is a proxy/CDN failure. This is not a grave error; there's a chance that the retry will succeed. In the worst case the job will fail after 3 identical errors (except SyncJob that will try to get through forever - but SyncJob failures should still be indicated in the client's UI in some non-intrusive way).
Diffstat (limited to '3rdparty')
0 files changed, 0 insertions, 0 deletions