8000 why use HTTP_CONTENT_RANGE to judge if chunked · Issue #71 · Gargron/fileupload · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
why use HTTP_CONTENT_RANGE to judge if chunked #71
New issue
New issue
Open
Open
why use HTTP_CONTENT_RANGE to judge if chunked#71
@zl-leaf

Description

@zl-leaf
zl-leaf
opened on Sep 7, 2018
example
request header
Range: bytes=0-2000

response header
Content-Range: bytes 0-2000/4932

but the library use $this->server['HTTP_CONTENT_RANGE'] in FileUpload.php to judge if chunked, is it correct?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0