[2.2.x] Fixed #30694 -- Documented FileResponse does not seek its file source.
Backport of 7203efb799
from master
This commit is contained in:
parent
6624a3de28
commit
556cef1ba8
|
@ -67,6 +67,7 @@ Here's a "Hello World" example::
|
|||
|
||||
# FileResponse sets the Content-Disposition header so that browsers
|
||||
# present the option to save the file.
|
||||
buffer.seek(0)
|
||||
return FileResponse(buffer, as_attachment=True, filename='hello.pdf')
|
||||
|
||||
The code and comments should be self-explanatory, but a few things deserve a
|
||||
|
|
|
@ -1106,6 +1106,8 @@ Attributes
|
|||
|
||||
If ``open_file`` doesn't have a name or if the name of ``open_file`` isn't
|
||||
appropriate, provide a custom file name using the ``filename`` parameter.
|
||||
Note that if you pass a file-like object like ``io.BytesIO``, it's your
|
||||
task to ``seek()`` it before passing it to ``FileResponse``.
|
||||
|
||||
The ``Content-Length``, ``Content-Type``, and ``Content-Disposition``
|
||||
headers are automatically set when they can be guessed from contents of
|
||||
|
|
Loading…
Reference in New Issue