client: Prohibit empty chunk responses for GET/RANGE/SEARCH #651
Labels
client
Issue related to the client
enhancement
Improving existing functionality
I3
Minimal impact
S3
Minimally significant
U4
Nothing urgent
Milestone
Is your feature request related to a problem? Please describe.
currently,
Client
does not consider empty chunk responses (*) with OK status invalid. At the same time, now this can only signal a buggy server: an empty message loads the network, + cryptography, and carries nothing. Being transmitted, they are silently reducing system performance(*) note that SEARCH stream with a single empty message is valid cuz it means not found
if server will start spamming empty chunks for whatever reason, the
Client
will hang doing a lot of useless work. The only savior will be the context deadline (if set)Describe the solution you'd like
prohibit empty data chunks, react with corresponding error
Describe alternatives you've considered
try to find potential benefits in them. I see no
Additional context
Client
testingThe text was updated successfully, but these errors were encountered: