it sounds like a compatibility issue between swift's s3 middleware and the actual s3 behavior, hence a bug in swift's s3 middleware compatibility. we could try to address in txaws s3 implementation as a workaround, but that's not quite right..
looking over the s3 swift middleware history this is the commit that causes the issue
its basically disallowing a time delta of more 1m from the server current time, which is broken for this case, in addition to parsing it with the wrong format.
it sounds like a compatibility issue between swift's s3 middleware and the actual s3 behavior, hence a bug in swift's s3 middleware compatibility. we could try to address in txaws s3 implementation as a workaround, but that's not quite right..
looking over the s3 swift middleware history this is the commit that causes the issue
https:/ /github. com/fujita/ swift3/ commit/ c3341b8de8befc7 ed6dfca94de7090 4baa853c61
its basically disallowing a time delta of more 1m from the server current time, which is broken for this case, in addition to parsing it with the wrong format.