summaryrefslogtreecommitdiff
path: root/po/pt_BR.po
diff options
context:
space:
mode:
authorDavid Kalnischkies <kalnischkies@gmail.com>2013-09-16 23:21:11 +0200
committerDavid Kalnischkies <kalnischkies@gmail.com>2013-10-01 11:04:14 +0200
commit331e8396ee5a4f2e7d276eddc54749b2a13dd789 (patch)
tree7b01e67de8faaf7ffbc6ea27b89ad6a50b64b157 /po/pt_BR.po
parent14c84d021d82335255275f1eabf3a856bde4df07 (diff)
retry without partial data after a 416 response
If we get a 416 from the server it means the Range we asked for is above the real filesize of the file on the server. Mostly this happens if the server isn't supporting If-Range, but regardless of how we end up with the partial data, the data is invalid so we discard it and retry with a fresh plate and hope for the best. Old behavior was to consider 416 an error and retry with a different compression until we ran out of compression and requested the uncompressed file (which doesn't exist on most mirrors) with an accept line which server answered with "406 Not Acceptable". Closes: 710924
Diffstat (limited to 'po/pt_BR.po')
0 files changed, 0 insertions, 0 deletions