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

single byte content-range prefix #154

Open
annevk opened this issue Jan 22, 2021 · 1 comment
Open

single byte content-range prefix #154

annevk opened this issue Jan 22, 2021 · 1 comment
Assignees
@jakearchibald

Comments

@annevk
Copy link

annevk commented Jan 22, 2021 •
edited
Loading

This suggests "bytes=" is the prefix whereas per the RFCs it appears to be "bytes " (i.e., trailing space, no trailing equals sign).

Might be worth capturing this difference in tests now this has been out there this long.
@jakearchibald jakearchibald self-assigned this Jan 22, 2021
@jakearchibald
Copy link
Collaborator

Oops. Good catch.

@annevk annevk mentioned this issue Jan 22, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jakearchibald jakearchibald

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jakearchibald @annevk