You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* test: suffix range request
* chore: adjust range to not start at 0
makes test more representative of seeking inside of a partially
available file
* chore: focus on Content-Range
content-type is not hard requirement, and implementations may have
easier or harder time with coming up with the right one.
if the content type info is not part of DAG metadata, and needs to me
sniffed (majority of content in 2025), then this internal sniffing may
produce different results in different file x library permutations.
in practice, it does not matter, browsers will stream videos just fine.
lets focus on Content-Range and body being correct - if we need to test
Content-Type, let's move it to a different test suite
* chore: human-readable check results
* test: Accept-Ranges: bytes present
ensure behavior described in
ipfs/boxo#856 (comment)
is covered by test
* chore: release as 0.8.0
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
4
4
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
5
5
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
7
+
## [0.8.0] - 2025-05-28
8
+
### Changed
9
+
- Comprehensive tests for HTTP Range Requests over deserialized UnixFS files have been added. The `--specs path-gateway` now requires support for at least single-range requests. Deserialized range-requests can be skipped with `--skip 'TestGatewayUnixFSFileRanges'`[#213](https://github.com/ipfs/gateway-conformance/pull/213)
Name: "GET for /ipfs/ file with multiple range request returned HTTP 206",
537
+
Hint: "This test reads Content-Type and Content-Range of response, which enable later tests to check if response was acceptable (either single range, or multiple ones)",
t.Error("Content-Type header did not match any of the accepted options")
611
+
t.Error("Content-Range and Content-Type header did not match any of the accepted options for a Range request (neither single or multiple ranges are supported)")
597
612
}
598
613
614
+
// Range request should work when unrelated parts of DAG not available.
0 commit comments