Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

need support of multipart/byteranges RFC 2616 14.16 #232

Open
GoogleCodeExporter opened this issue Nov 4, 2015 · 1 comment
Open

need support of multipart/byteranges RFC 2616 14.16 #232

GoogleCodeExporter opened this issue Nov 4, 2015 · 1 comment
Labels
auto-migrated Priority-High Type-Defect

Comments

@GoogleCodeExporter
Copy link 

I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994, 
1834896-1836229, 1844508-1846009, 1837995-1841917, 1844311-1844507, 
617450-639641

Mongoose handles only the first content-range.
But according to RFC 2616 par 14.16 resp. appendix 19.2
it should answer with multipart/byteranges

Original issue reported on code.google.com by holger.g...@googlemail.com on 16 Feb 2011 at 10:19
@GoogleCodeExporter
Copy link
Author

Original comment by valenok on 22 Jun 2011 at 1:26

  • Changed state: Accepted
  • Added labels: Priority-High
  • Removed labels: Priority-Medium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-High Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter