ECS: Incorrect HTTP 500 Error on malformatted Bucket Policy

An attempt to set a S3 bucket policy is made using S3 API where "Statement" elements are missing the "Resource" section. See the Admin guide for more details on bucket policies.
The ECS replies incorrectly with "HTTP/1.1 500 Internal server error" response.
The reply is not implying that the request is invalid.

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

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'

The ECS returns an incorrect response for the malformatted request.

According to RFC 9110, the correct response should be:

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).

The response had been corrected from ECS 3.8.1.3 and ObjectScale 4.0 and later.