maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

fixing cross-referenced links on fileupload patterns page

Browse source
This commit is contained in:
matt swanson 2011-03-13 15:47:40 -09:00
parent 6bdde49348
commit 4046d3bd30
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/patterns/fileuploads.rst
View file

@ -10,7 +10,7 @@ uploads is actually quite simple. It basically works like this:
and an ``<input type=file>`` is placed in that form. and an ``<input type=file>`` is placed in that form.
2. The application accesses the file from the :attr:`~flask.request.files` 2. The application accesses the file from the :attr:`~flask.request.files`
dictionary on the request object. dictionary on the request object.
3. use the :meth:`~werkzeug.FileStorage.save` method of the file to save 3. use the :meth:`~werkzeug.datastructures.FileStorage.save` method of the file to save
the file permanently somewhere on the filesystem. the file permanently somewhere on the filesystem.
A Gentle Introduction A Gentle Introduction
@ -71,7 +71,7 @@ the file and redirects the user to the URL for the uploaded file::
</form> </form>
''' '''
So what does that :func:`~werkzeug.secure_filename` function actually do? So what does that :func:`~werkzeug.utils.secure_filename` function actually do?
Now the problem is that there is that principle called "never trust user Now the problem is that there is that principle called "never trust user
input". This is also true for the filename of an uploaded file. All input". This is also true for the filename of an uploaded file. All
submitted form data can be forged, and filenames can be dangerous. For submitted form data can be forged, and filenames can be dangerous. For
@ -80,7 +80,7 @@ before storing it directly on the filesystem.
.. admonition:: Information for the Pros .. admonition:: Information for the Pros
So you're interested in what that :func:`~werkzeug.secure_filename` So you're interested in what that :func:`~werkzeug.utils.secure_filename`
function does and what the problem is if you're not using it? So just function does and what the problem is if you're not using it? So just
imagine someone would send the following information as `filename` to imagine someone would send the following information as `filename` to
your application:: your application::
@ -109,7 +109,7 @@ Flask 0.5 we can use a function that does that for us::
filename) filename)
Alternatively you can register `uploaded_file` as `build_only` rule and Alternatively you can register `uploaded_file` as `build_only` rule and
use the :class:`~werkzeug.SharedDataMiddleware`. This also works with use the :class:`~werkzeug.wsgi.SharedDataMiddleware`. This also works with
older versions of Flask:: older versions of Flask::
from werkzeug import SharedDataMiddleware from werkzeug import SharedDataMiddleware