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

Fix ContentRange parser #449

Closed
wants to merge 1 commit into from
Closed

Fix ContentRange parser #449

wants to merge 1 commit into from

Conversation

SchwingSK
Copy link

It failed to parse valid Content-Range headers
Closes #65563

It failed to parse valid Content-Range headers
Closes #65563
markt-asf added a commit that referenced this pull request Sep 9, 2021
Tomcat was incorrectly requiring an '=' character after "bytes". Fix
based on pull request #449  by Thierry Guérin.
markt-asf added a commit that referenced this pull request Sep 9, 2021
Tomcat was incorrectly requiring an '=' character after "bytes". Fix
based on pull request #449  by Thierry Guérin.
markt-asf added a commit that referenced this pull request Sep 9, 2021
Tomcat was incorrectly requiring an '=' character after "bytes". Fix
based on pull request #449  by Thierry Guérin.
markt-asf added a commit that referenced this pull request Sep 9, 2021
Tomcat was incorrectly requiring an '=' character after "bytes". Fix
based on pull request #449  by Thierry Guérin.
@markt-asf
Copy link
Contributor

Thanks for the PR. I applied the PR manually as I wanted to make a few changes:

  • add a comment explaining why we don't explicitly parse for SP
  • add some additional tests
  • add a change log entry

@markt-asf markt-asf closed this Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants