On Nov 17 2015, Daniel Jagszent <[email protected]> wrote: > Cyberduck (like s3ql) sets the |Connection: keep-alive| header, but the > server chooses to not honor that request and sends the |Connection: > close| response header (and subsequently closes the connection, of course). > > This is not nice of the server but perfectly valid according to RFC 2616 > Section 8.1.2.1 ( http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html ) > > Am I right in assuming that s3ql can not handle the server choosing to > close the persistent connection and that's what these retry error > messages are?
That's most likely correct, but shouldn't be too hard to fix. Could you file a bug at https://bitbucket.org/nikratio/s3ql/issues? Best, Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
