ECS：格式錯誤的容器原則上的不正確 HTTP 500 錯誤

嘗試使用 S3 API 設定 S3 儲存桶原則，其中「語句」元素缺少「資源」區段。有關存儲桶策略的更多詳細資訊，請參閱管理員指南。
彈性雲伺服器以「HTTP/1.1 500 內部伺服器錯誤」回應錯誤地回復。
答覆並不意味著請求無效。

##################################################

Reqid: REQ123456789
Reply timestamp: 2024-07-23T14:15:16,123
Protocol: s3
Request Type: PUT
Size: 1429 Bytes (0.001 MB)
Response Time: 11 ms
Full Target: exampleNamespace/exampleBucket/exampleObject/?policy
Namespace: exampleNamespace
Bucket: exampleBucket
Object (reformatted): exampleObject/
Object (as sent): exampleObject%2F
Options: ?policy
Status: 500
Server IP: 192.0.2.1
Client IP: 192.0.2.2
Client User: anonymousUser
Browser User-Agent: -

Request (or retry)
completed: No
Retry #: 0 (of 0 total)

Original line:
2024-02-27 15:04:19,253 REQ123456789 192.0.2.1:9020 192.0.2.2:48300 anonymousUser - PUT exampleNamespace exampleBucket exampleObject%2F policy HTTP/1.1 500 11 1429 - 7 - - - - 'x-amz-content-sha256: ' 'x-amz-date: 2024-07-23T14:15:16,123' 'content-type: application/json' 'Accept-Encoding: identity'

彈性雲伺服器對格式錯誤的請求返回不正確的回應。

根據 RFC 9110，正確的回應應該是：

400 Bad Request
400 (Bad Request) status code indicates that the server cannot or will not process the request due to something perceived
 to be a client error.(e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

回應已從 ECS 3.8.1.3 和 ObjectScale 4.0 及更新版本更正。