Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Empty Content-Type violating RFC2616 #6181

Closed
cyberduck opened this issue Aug 30, 2011 · 7 comments
Closed

Empty Content-Type violating RFC2616 #6181

cyberduck opened this issue Aug 30, 2011 · 7 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
4.1.3

Comments

@cyberduck
Copy link
Collaborator

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
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

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
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

@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
Copy link
Collaborator Author

@dkocher commented

The issue is reported against Jets3t in issue 109.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Updated library with patch included in 6083a49.

@cyberduck
Copy link
Collaborator Author

Tingjun Li commented

Good job! Thanks! :-)

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.1.3
Development

No branches or pull requests
2 participants
@dkocher @cyberduck