On Tue, Aug 30, 2011 at 10:00 AM, Isaac Li <tingjun...@gmail.com> wrote:
> Thank André and Mark for your quick response, detailed answer and > references! > > I'll try to report this issue to Cyberduck. > > One more question: when I uses current version of Cyberduck to connect > Amazon S3, > See request at No.25 of "Cyberduck_login_amazon_s3_ok.pcap" (attched) GET / HTTP/1.1 Date: Tue, 30 Aug 2011 02:28:50 GMT Content-Type: Authorization: AWS AKIAJHSWPWM6W6KUXAIQ:u4QnOMbP0vuTsgpUXQ0WfXIWz9c= Host: s3.amazonaws.com:80 Connection: Keep-Alive User-Agent: Cyberduck/4.1 (8911) (Windows 7/6.1) (x86) Accept-Encoding: gzip,deflate > it can accept this kind of invalid request, > request at No.31 of Cyberduck_login_amazon_s3_ok.pcap 31 5.805868 207.171.189.80 192.168.1.104 HTTP/XML 64 HTTP/1.1 200 OK > Is it a kind of fault tolerance design of Amazon S3? Should it be > encouraged? or I missed something here? >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
