secondlife / secondlife/viewer
corehttp - Content-Range - Update Content-Range parsing to support changes from RFC7233 (and beyond)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Any 2025.05 and earlier viewer. All platforms.
Description
RFC7233 introduces new 'Content-Range' syntax on responses. In the case of 416 returns, servers may send:
Content-Range: */<NNN>
and the CDN is starting to issue those, at least on Firestorm. The viewer fails to parse this and issues an INFO-level log event and then goes on to deal with the 416. (Correctly, I believe, in the SL case.)
Would be good to parse this new form, avoid the logging, and continue handling the request as a basic 416 failure in HttpOpRequest::headerCallback() where parse_content_range_header() is called.
Scenario will also exist in simulator's copy.
Reproduction steps
Read the log files.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at HttpOpRequest::headerCallback() and the parse_content_range_header() call, then inspect how the current parser handles a 416 response. Support the Content-Range: */ form without the INFO-level log while preserving basic 416 handling, and check the simulator's copy for the same scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100