Skip to content

single byte content-range prefix #154

Open

Description

@annevk

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.

Activity

  1. jakearchibald commented on Jan 22, 2021

    @jakearchibald
    Collaborator

    Oops. Good catch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions