Hi Sidnei, Great work! The file pointer position crossed my mind, but the 400 Bad Request was throwing me off.
I now see the commit that broke this: http://bazaar.launchpad.net /~duplicity-team/duplicity/0.6-series/revision/901 in duplicity/backends/u1backend.py. It went from using a bytearray to using the file pointer as you mention. Of course when using the bytearray, it will begin at the front when retrying. I also noticed that in that same commit, the Content-Length header was removed. I believe this is wrong as well based on the U1 API documentation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161599 Title: Backup to Ubuntu one failed, after 5 attempts status 400 bad request To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1161599/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
