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

[Cyberduck]

#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:            |
----------------------+-------------------------
Changes (by tschop):

 * status:  closed => reopened
 * resolution:  thirdparty =>


Comment:

 Unfortunately the workaround in the Nginx configuration doesn't work as
 expected. We use Nginx as a pure proxy, and because Nginx try to minimize
 the communication with the backend, it will not forward the "Expect:
 100-continue". It is the default behaviour of Nginx, and it is not
 possible to disable it.

 > We add a Expect: 100-continue to all PUT requests and include it in the
 AWS4-HMAC-SHA256 signature.

 Why do you include the Expect header in the AWS4 SignedHeaders signature?
 This header is not relevant for the content of the request, and does not
 carry any useful information.

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