[Cyberduck-trac] [Cyberduck] #10170: Does not send the Expect header, but adds it in the list of the SignedHeaders for AWS4 signature

Cyberduck trac at cyberduck.io
Wed Jan 10 08:22:53 UTC 2018


#10170: Does not send the Expect header, but adds it in the list of the
SignedHeaders for AWS4 signature
----------------------+-------------------------
 Reporter:  zioproto  |         Owner:  dkocher
     Type:  defect    |        Status:  reopened
 Priority:  normal    |     Milestone:  6.3.2
Component:  s3        |       Version:  6.3.1
 Severity:  normal    |    Resolution:
 Keywords:            |  Architecture:
 Platform:            |
----------------------+-------------------------

Comment (by zioproto):

 I would also strongly suggest not to include in the signature the
 {{{Expect}}} header.
 To make S3-like storage solutions scale horizontally, there is often a
 reverse proxy in front of the storage backend, that might not forward the
 {{{Expect}}} header.
 This header has always the same content string '100-continue', and this
 makes including in the signature this header nonsense.

 Thank you

--
Ticket URL: <https://trac.cyberduck.io/ticket/10170#comment:10>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list