Empty Content-Type violating RFC2616

[cyberduck]

Tingjun Li created the issue

Hello,

I'm using Cyberduck/4.1 (8911) to create a S3/HTTP(Amazon Simple Storage Service) connection, it send request with an empty Content-Type which is violating RFC2616. Please have a look at this issue, thanks. (Wireshark cap file attached.)

---

Attachments

• Cyberduck_login_amazon_s3.pcap (6.7 KiB)

[cyberduck]

@dkocher commented

Is this giving a blocking issue? Just to know what priority to assign.

[cyberduck]

Tingjun Li commented

Replying to [comment:1 dkocher]:

Is this giving a blocking issue? Just to know what priority to assign.

It's OK with connecting S3 but failed with connecting some other S3-compatible services (has not been public currently)

[cyberduck]

@dkocher commented

Can you just attach the transcript from the log drawer (⌘-L) of the Transfers and Browser windows.

[cyberduck]

@dkocher commented

GET / HTTP/1.1
Date: Wed, 31 Aug 2011 15:16:17 GMT
Content-Type: 
Authorization: AWS XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=
Host: s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.1.2 (Mac OS X/10.6.8) (i386)

[cyberduck]

@dkocher commented

The issue is reported against Jets3t in issue 109.

[cyberduck]

@dkocher commented

Updated library with patch included in 6083a49.

[cyberduck]

Tingjun Li commented

Good job! Thanks! :-)