Steps to reproduce.
1. Create file hamandeggs.txt which contains "hamandeggs"
2. Put the file to S3
3. $ echo -n ham > hamandeggs.txt
4. $ s3cmd -c /path/to/.s3cfg get --continue s3://shino.shun.test1/hamandeggs.txt
Actual result:
$ cat hamandeggs.txt
hamhamandeggs
Expected results:
$ cat hamandeggs.txt
hamandeggs
Look into packet capture,
S3 responds 307 to GET request.
In the next GET request, no Range header is included.
So S3 responds full resource.