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

Response currectly to Range #116

Merged
merged 6 commits into from
Mar 14, 2023
Merged

Response currectly to Range #116

merged 6 commits into from
Mar 14, 2023

Commits on Mar 13, 2023

  1. Parse range in header.

    @Berrysoft
    Berrysoft committed Mar 13, 2023
    Configuration menu
    Copy the full SHA
    a4f28f6 View commit details
    Browse the repository at this point in the history

  2. Remove chunked body.

    @Berrysoft
    Berrysoft committed Mar 13, 2023
    Configuration menu
    Copy the full SHA
    92080d3 View commit details
    Browse the repository at this point in the history

  3. Get length only when asking ranges.

    @Berrysoft
    Berrysoft committed Mar 13, 2023
    Configuration menu
    Copy the full SHA
    7212996 View commit details
    Browse the repository at this point in the history

  4. Simplify headers.

    @Berrysoft
    Berrysoft committed Mar 13, 2023
    Configuration menu
    Copy the full SHA
    883b180 View commit details
    Browse the repository at this point in the history

Commits on Mar 14, 2023

  1. Deal with invalid range correctly.

    @Berrysoft
    Berrysoft committed Mar 14, 2023
    Configuration menu
    Copy the full SHA
    d97e8d0 View commit details
    Browse the repository at this point in the history

  2. Use read_buf_exact.

    @Berrysoft
    Berrysoft committed Mar 14, 2023
    Configuration menu
    Copy the full SHA
    4418810 View commit details
    Browse the repository at this point in the history