When return a big file by FileResponse, How to realize resuming transfer on the server side

[jl7599]

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to FastAPI but to Pydantic.
• I already checked if it is not related to FastAPI but to Swagger UI.
• I already checked if it is not related to FastAPI but to ReDoc.
• After submitting this, I commit to one of:
  • Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
  • I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
  • Implement a Pull Request for a confirmed bug.

Example

Here's a self-contained, minimal, reproducible, example with my use case:

from fastapi import FastAPI
from fastapi.response import FileResponse

app = FastAPI()


@app.get("/download")
def downlaod_file():
    file_path = "/tmp/large.tar.gz"
    return FileResponse(file_path)

Description

• wget -c http://127.0.0.1/download, and then Crtl + c abort this download, how to download from the existing file again
• like flask.send_file conditional param
• I know FileResponse support custom headers, and how to handle this custom headers

Environment

• OS: Ubuntu 18.04
• python version: 3.7.4
• FastAPI Version : 0.61.0

[phy25]

See encode/starlette#950

[tiangolo]

Thanks for the help @phy25 ! 🙇

Yep, that would be a request in Starlette, not in FastAPI. 🤓

[github-actions]

Assuming the original need was handled, this will be automatically closed now. But feel free to add more comments or create new issues or PRs.