summaryrefslogtreecommitdiff
path: root/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_1_533c4a26200501486a9ec103e1301391._comment
blob: 8921214a92b7b390b7e4ea6b6ad513e85b80b2c1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
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.
"""]]