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