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

S3: Enable debug logging when annex.debug or --debug is set.

Browse source 
To debug a bug report, but generally useful.
This commit is contained in:
Joey Hess 2015-04-21 15:55:42 -04:00
parent a7c35d6961
commit 3b3aaf0d56
3 changed files with 32 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_1_533c4a26200501486a9ec103e1301391._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-04-21T19:23:18Z"
content="""
So the http 301 redirect seems to be the relevant clue.
Perhaps the old S3 library followed such redirects and the new aws library
does not. Although AFAICS, http-client should follow redirects by default.
Are you able to store new files in this remote and get them back out?
Which Amazon datacenter is the bucket at?
I've added some more debugging to the S3 remote; --debug will now
have it log the http requests and responses. Perhaps this will give us
more clues to the problem.
"""]]