Documentation, Release 6.1 Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

forgery protection Running and deploying Processes and ports Running behind a load balancer Static files and aggressive file caching Debug mode and automatic reloading WSGI and Google App Engine Introduction their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary 21 Tornado Documentation, Release 5.1.1 "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body

their singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary dictionary of the form {"filename":..., "content_type":..., "body":...}. The files object is only present if the files were uploaded with a form wrapper (i.e. a multipart/form-data Content-Type); if this format uploaded data is available in self.request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body