mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

comment

Browse source
This commit is contained in:
Joey Hess 2020-01-06 13:59:03 -04:00
parent 84960da522
commit d9ed94f15b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/todo/S3_special_remote_support_for_DigitalOcean_Spaces/comment_1_12fd9dfb47e157e1d38c5e88a543498b._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-01-06T17:41:21Z"
content="""
This is either a bug in <http://hackage.haskell.org/package/aws> or
Digital Ocean's implementation of the S3 protocol. I don't know which,
but I do know it has to be fixed in one of those two place, and not
in git-annex.
The fact that the aws library can't even parse an error message out of
their response kind of says something.
But the real problem seems to
While they claim to support V2 signatures,
my guess is there's a problem with their support for V2, since they're
mostly dealing with V4. The aws library's support for V4 is experimental
and [apparently buggy](https://github.com/aristidb/aws/issues/262), but
as git-annex uses it, it will only use V2.
"""]]