[ 
https://issues.apache.org/jira/browse/HDDS-12842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944905#comment-17944905
 ] 

Ivan Andika commented on HDDS-12842:
------------------------------------

Seems Jetty will handle the "Expect: 100-continue" header automatically by 
responding immediately.

https://github.com/jetty/jetty.project/blob/e3fa9466633db6bf36e0eb0d17e3de166c788ede/jetty-server/src/main/java/org/eclipse/jetty/server/HttpChannelOverHttp.java#L206

> Handle "Expect: 100-continue" header
> ------------------------------------
>
>                 Key: HDDS-12842
>                 URL: https://issues.apache.org/jira/browse/HDDS-12842
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ivan Andika
>            Assignee: Ivan Andika
>            Priority: Major
>         Attachments: image-2025-04-16-10-39-33-154.png
>
>
> AWS S3 SDK might send "Expect: 100-continue" header for PUT request 
> (UploadObject / UploadPart) to check whether there are available space before 
> sending the actual content data. For example AWS Go SDK will add the "Expect: 
> 100-Continue" header when the request is larger than 2MB (or in some case if 
> there is an unknown-size body).
> Currently Ozone does not handle this, we need to check whether we should 
> support this. There might be some functionality or performance impact.
> We found a user that intermittently received this error
> {code:java}
> InternalError: Header expect not present in request but requested to be 
> signed.\n\tstatus code: 500, request id: 
> 28c2d896-d04c-4068-b854-9b036c03671f, host id: mQxBdH9Q8loGf {code}
> Links: 
>  * 
> [https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html]
>  * AWS Go SDK
>  ** V1: 
> [https://github.com/aws/aws-sdk-go/blob/main/service/s3/platform_handlers_go1.6.go]
>  
>  ** V2: [https://github.com/aws/aws-sdk-go-v2/pull/2051]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to