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.

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

Content-Range header parsing * comparison #155

Open
annevk opened this issue Jan 22, 2021 · 0 comments
Open

Content-Range header parsing * comparison #155

annevk opened this issue Jan 22, 2021 · 0 comments
Assignees

Comments

@annevk
Copy link

annevk commented Jan 22, 2021

It seems that * in the algorithm is a byte, not a string, so it should use the backtick syntax, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants