jakearchibald / jakearchibald/accept-encoding-range-test
A couple of thoughts
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
`Range: bytes=0-` can be interpreted by servers as "the whole thing", so it's not surprising that they might think they can send back a 200. A more interesting test would be something like `Range: bytes=20-200` (depending on the size of the response body).
Also, I very much wonder if anything would change if you send `If-Range`...
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the request with `Range: bytes=20-200` and compare the server response with the existing `bytes=0-` case. Then investigate whether adding `If-Range` changes the result. Done means the relevant range and conditional-range behavior is covered by the test setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100