wip: http range with file-3k-and-3-blocks-missing-block.car #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Results against Kubo master: Summary
|
|
Results against Kubo latest: Summary
|
lidel
commented
Jun 9, 2024
| Headers( | ||
| // TODO: fix HTTP 500: cannot detect content-type: failed to fetch all nodes i boxo/gateway (or create better fixture that does not clash with content-type sniffing logic) | ||
| Header("Content-Type").Contains("text/plain"), | ||
| Header("Content-Range").Equals("bytes 0-1000/31"), |
There was a problem hiding this comment.
💭 switch to size form unixfs, once HTTP 500 is resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is WIP port of HTTP Range tests described in #154 (comment)
cannot detect content-type: failed to fetch all nodesreturned right now by boxo/gateway (or create better fixture that does not clash with content-type sniffing logic)Aims to close #154 (comment)