client: Prohibit empty chunk responses for GET/RANGE/SEARCH #248

New issue

Open

opened 2025-12-28 18:07:34 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:07:34 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 6, 2024).

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 testing

Originally created by @cthulhu-rider on GitHub (Dec 6, 2024). ## 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` testing