Revise fallback to GET when no RANGE access #1490

New issue

Open

opened 2025-12-28 17:23:10 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:23:10 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Aug 28, 2025).

I'm always frustrated when RANGE access is denied while GET is not. RANGE is a trivial operation around GET: take full object and make a cut. However, the system does not have this implication

in particular, 4baf00aa21 was done once. It looks weakly effective:

smaller RANGE requested, bigger overhead GET brings
RANGE and GET are either allowed both or forbidden both in most cases, so fallback hardly helps

Describe the solution you'd like

allow to RANGE and HEAD when GET is allowed
drop fallback
allow in-container nodes to RANGE

note that 1 implies 3

Describe alternatives you've considered

2 and/or 3 but not 1

Additional context

#3546

Originally created by @cthulhu-rider on GitHub (Aug 28, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when RANGE access is denied while GET is not. RANGE is a trivial operation around GET: take full object and make a cut. However, the system does not have this implication in particular, 4baf00aa214e168f26f9b41217b5e25882ad0186 was done once. It looks weakly effective: 1. smaller RANGE requested, bigger overhead GET brings 2. RANGE and GET are either allowed both or forbidden both in most cases, so fallback hardly helps ## Describe the solution you'd like 1. allow to RANGE and HEAD when GET is allowed 2. drop fallback 3. allow in-container nodes to RANGE note that 1 implies 3 ## Describe alternatives you've considered 2 and/or 3 but not 1 ## Additional context #3546

sami added the

enhancement

neofs-storage

labels

2025-12-28 17:23:10 +00:00

sami commented

2025-12-28 17:35:37 +00:00

Author

Owner

@roman-khimov commented on GitHub (Sep 4, 2025):

allow to RANGE and HEAD when GET is allowed

This reminds of https://github.com/nspcc-dev/neofs-api/issues/273, but as much as I'd like to change some things, we need to keep compatibility.

drop fallback
allow in-container nodes to RANGE

This looks more feasible. Container nodes have data anyway.

@roman-khimov commented on GitHub (Sep 4, 2025): > allow to RANGE and HEAD when GET is allowed This reminds of https://github.com/nspcc-dev/neofs-api/issues/273, but as much as I'd like to change some things, we need to keep compatibility. > drop fallback > allow in-container nodes to RANGE This looks more feasible. Container nodes have data anyway.