Skip to content

Conversation

@ritik4ever
Copy link

@ritik4ever ritik4ever commented Dec 27, 2025

  • Implement FileRangeSupport for serving files with Range header support
  • Support single range requests (206 Partial Content)
  • Support multiple range requests (multipart/byteranges)
  • Handle unsatisfiable ranges (416 Range Not Satisfiable)
  • Handle suffix ranges (last N bytes)
  • Add comprehensive test suite
  • Add example application
  • Utilize existing Range, ContentRange, and AcceptRanges headers

Fixes
Close #709
/claim #709

- Implement FileRangeSupport for serving files with Range header support
- Support single range requests (206 Partial Content)
- Support multiple range requests (multipart/byteranges)
- Handle unsatisfiable ranges (416 Range Not Satisfiable)
- Handle suffix ranges (last N bytes)
- Add comprehensive test suite
- Add example application
- Utilize existing Range, ContentRange, and AcceptRanges headers

Fixes zio#709
@netlify
Copy link

netlify bot commented Dec 27, 2025

Deploy Preview for zio-http ready!

Name Link
🔨 Latest commit 3a95d5e
🔍 Latest deploy log https://app.netlify.com/projects/zio-http/deploys/69500af6b355d5000866a3b4
😎 Deploy Preview https://deploy-preview-3875--zio-http.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@CLAassistant
Copy link

CLAassistant commented Dec 27, 2025

CLA assistant check
All committers have signed the CLA.

- Use Body.fromStreamChunked instead of Body.fromStream
- Use Status.Custom(416) for Range Not Satisfiable
- Fix ZStream.fromZIO pattern
- Use java.lang.System.currentTimeMillis() instead of zio.System
- Use Body.fromStreamChunked for proper codec support
- Use Status.Custom(416) for Range Not Satisfiable
- Fix ZStream pattern with fromZIO
- Use java.lang.System for currentTimeMillis
Copy link
Author

@ritik4ever ritik4ever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've submitted PR #3875 that implements HTTP Range request support. The implementation includes:

  • Single range requests (206 Partial Content)
  • Multiple range requests (multipart/byteranges)
  • Suffix ranges (last N bytes)
  • Proper error handling (416 Range Not Satisfiable)
  • Comprehensive test suite
  • Working example application

Would appreciate any feedback!

@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

👋 This PR is being automatically closed because it has had a failed CI build for over 3 days.

If you're still working on this, please:

  1. Fix any failing tests or build issues
  2. Push your changes
  3. Reopen this PR once the build passes

Thank you for your contribution! 🙏

@github-actions github-actions bot closed this Jan 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Http Range header on request for Files

2 participants