Task #7821
Updated by Robert Waltz almost 8 years ago
see https://redmine.dataone.org/issues/2693 for context
We may be are adding support on the CNs a conditional that will turn off SSL verification for the 100-Continue header in order to successfully upload content Safari browser (SSLVerifyClient none). Chris noted that on some a member node servers.
where this was done, the client for uploading content began to fail. Once the header 'Expect: 100-Continue' was added to the requests, uploading was successful.
The same problem is described here:
http://stackoverflow.com/questions/14281628/ssl-renegotiation-with-client-certificate-causes-server-buffer-overflow
More description of the header's use from a Java client:
'Expect: 100-Continue' handshake for the entity enclosing methods.
The purpose of the Expect: 100-Continue handshake is to allow the client
that is sending a request message with a request body to determine if
the origin server is willing to accept the request (based on the request
headers) before the client sends the request body. The use of the
Expect: 100-continue handshake can result in a noticeable performance
improvement for entity enclosing requests (such as POST and PUT) that
require the target server's authentication.
https://hc.apache.org/httpcomponents-client-4.2.x/tutorial/html/fundamentals.html
We may be are adding support on the CNs a conditional that will turn off SSL verification for the 100-Continue header in order to successfully upload content Safari browser (SSLVerifyClient none). Chris noted that on some a member node servers.
where this was done, the client for uploading content began to fail. Once the header 'Expect: 100-Continue' was added to the requests, uploading was successful.
The same problem is described here:
http://stackoverflow.com/questions/14281628/ssl-renegotiation-with-client-certificate-causes-server-buffer-overflow
More description of the header's use from a Java client:
'Expect: 100-Continue' handshake for the entity enclosing methods.
The purpose of the Expect: 100-Continue handshake is to allow the client
that is sending a request message with a request body to determine if
the origin server is willing to accept the request (based on the request
headers) before the client sends the request body. The use of the
Expect: 100-continue handshake can result in a noticeable performance
improvement for entity enclosing requests (such as POST and PUT) that
require the target server's authentication.
https://hc.apache.org/httpcomponents-client-4.2.x/tutorial/html/fundamentals.html
