Amit Mishra cb41e42d04 fs: fix negative offset when a suffix Range request exceeds object size ...

A Range header requesting a suffix longer than the object (e.g.
"bytes=-90407" against a 5 byte object) caused RangeOption.Decode to
compute a negative offset (size - End), which serve.Object then used
directly as a slice/seek offset and panicked with "slice bounds out of
range". FixRangeOption (used by backends like OneDrive/Box that lack
native suffix-range support) had the same root cause: it produced a
RangeOption with a negative Start, which Header() silently dropped,
turning the request into the wrong byte range instead of erroring or
serving the whole object.

Per RFC 7233 section 2.1, when the suffix-length exceeds the
representation size, the entire representation should be served.
Clamp the computed offset/start to 0 in both places.

Fixes #6310

2026-07-04 09:11:52 +01:00

..

dir_test.go

serve http: download folders as zip

2025-09-26 15:18:02 +01:00

dir.go

serve http: add gzip compression

2026-02-26 17:18:52 +00:00

serve_test.go

fs: fix negative offset when a suffix Range request exceeds object size

2026-07-04 09:11:52 +01:00

serve.go

http: add basic metadata and provide it via serve

2025-11-17 16:52:30 +00:00