From d81d8c8d3cdd9fd782bcdc0bf1442409e2d8d902 Mon Sep 17 00:00:00 2001 From: Marcelo Trylesinski Date: Sat, 6 Aug 2022 23:46:06 +0200 Subject: [PATCH] Update requests.md (#1792) --- docs/requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/requests.md b/docs/requests.md index a50c0753..747e496d 100644 --- a/docs/requests.md +++ b/docs/requests.md @@ -144,8 +144,8 @@ contents = await form["upload_file"].read() !!! info As settled in [RFC-7578: 4.2](https://www.ietf.org/rfc/rfc7578.txt), form-data content part that contains file - assumed to have `name` and `filename` fields in `Content-Disposition` header: `Content-Disposition: form- - data; name="user"; filename="somefile"`. Though `filename` field is optional according to RFC-7578, it helps + assumed to have `name` and `filename` fields in `Content-Disposition` header: `Content-Disposition: form-data; + name="user"; filename="somefile"`. Though `filename` field is optional according to RFC-7578, it helps Starlette to differentiate which data should be treated as file. If `filename` field was supplied, `UploadFile` object will be created to access underlying file, otherwise form-data part will be parsed and available as a raw string.