Sebastián Ramírez <******@****.***> 1728247014 +0200

Sebastián Ramírez <******@****.***> 1728247014 +0200

Sebastián Ramírez <******@****.***> 1728247014 +0200

A `Request` also has a `request.receive`, that's a function to "receive" the body of the request.

The `scope` `dict` and `receive` function are both part of the ASGI specification.

And those two things, `scope` and `receive`, are what is needed to create a new `Request` instance.

associates association.aero association.museum assur.bj asti.it astronomy.museum asuke.aichi.jp at at-band-camp.net at.eu.org at.it at.md at.vg atami.shizuoka.jp ath.cx athleta atl.jelastic.vps-host.net atlanta.museum atm.pl ato.br atsugi.kanagawa.jp atsuma.hokkaido.jp attorney au au.eu.org auction audi audible audio audnedaln.no augustow.pl aukra.no aure.no aurland.no aurskog-holand.no aurskog-høland.no aus.basketball auspost austevoll.no austin.museum australia.museum austrheim.no authgear-staging.com...

```Python hl_lines="8"
{!> ../../docs_src/request_forms_and_files/tutorial001.py!}
```

////

The files and form fields will be uploaded as form data and you will receive the files and form fields.

And you can declare some of the files as `bytes` and some as `UploadFile`.

/// warning

Sebastián Ramírez <******@****.***> 1728247014 +0200

Sebastián Ramírez <******@****.***> 1728247014 +0200

Sebastián Ramírez <******@****.***> 1728247014 +0200

// to  be  correctly  handled.   For example, changes to st_atime or st_mtime
// (respectively, time of last access and time of last modification; see inode(7))
// do not require flushing because they are not necessary for a subsequent data
// read to be handled correctly. On the other hand, a change to the file size
// (st_size, as made by say ftruncate(2)), would require a metadata flush.
//