3
_TBg` @ sD d dl Z d dlZd dlZd dlZd dlZd dlmZ ddlmZ ddl m
Z
ddl m Z ddl m Z ddl m
Z
dd l mZ dd
l mZ dd lmZ dd lmZ dd
lmZ ddlmZ ddlmZ ddlmZ ddlmZ d dl m Z ej rd dl Z d dl!m"Z" d dl!m#Z# G dd deZG dd dZ$G dd de$eZ%dS ) N)BytesIO )_wsgi_decoding_dance)CombinedMultiDict)EnvironHeaders) FileStorage)ImmutableMultiDict)iter_multi_items) MultiDict)default_stream_factory)FormDataParser)Request)cached_property)environ_property) _get_server)get_input_stream)
BadRequest)WSGIApplication)WSGIEnvironmentc s e Zd ZU dZdZeje dZeje e Z
ej e
dZ eje
de
dNde
e
dd fdd
Zeejejd d d
d Zeejd gd f d d
ddZdOeje eje eje eje eje dddZee
dddZe dddZ ddddZ eje dddZ ddd d Z d dd d Z ddd d!Z!e"eje dd"d#Z#e$eje d$d%d&Z%e"edd'd(Z&e'j(dPe
d)e
ed*d+d,Z)e'j(dQe
d.e
ed*d/d,Z)dRe
e
e
ej*eef d*d0d,Z)e"d1dd2d3Z+e"d4dd5d6Z,e"d7dd8d9Z-eedd:d;Z.e"eddd?d&Z0e$e
d@dAd&Z1e$e
dBdCd&Z2e$e
dDdEd&Z3e4Z5eejej ddFdGZ4e6e6fZ7ej8ejejf 7dSe
e
e
ejej dHdIdJZ9e:ejdKdLdMZ; Z r; r= r2 r3 application s z(Request.application..applicationr )
exceptionsr> functoolswrapstcast)r; r= rC r2 )r> r; r= r3 rC s
zRequest.application)total_content_length content_typefilenamecontent_lengthr c C s t ||||dS )a Called to get a stream for the file upload.
This must provide a file-like class with `read()`, `readline()`
and `seek()` methods that is both writeable and readable.
The default implementation returns a temporary file if the total
content length is higher than 500KB. Because many browsers do not
provide a content length for the files only the total content
length matters.
:param total_content_length: the total content length of all the
data in the request combined. This value
is guaranteed to be there.
:param content_type: the mimetype of the uploaded file.
:param filename: the filename of the uploaded file. May be `None`.
:param content_length: the length of this file. This value is usually
not provided because webbrowsers do not provide
this value.
)rI rK rJ rL )r )r0 rI rJ rK rL r2 r2 r3 _get_file_stream s
zRequest._get_file_stream)r c C s t | jjdS )z``True`` if the request method carries content. By default
this is true if a ``Content-Type`` is sent.
.. versionadded:: 0.8
CONTENT_TYPE)boolr r( )r0 r2 r2 r3 want_form_data_parsed s z Request.want_form_data_parsedc C s | j | j| j| j| j| j| jS )zCreates the form data parser. Instantiates the
:attr:`form_data_parser_class` with some parameters.
.. versionadded:: 0.8
)form_data_parser_classrM r) r* max_form_memory_sizemax_content_lengthparameter_storage_class)r0 r2 r2 r3 make_form_data_parser s z Request.make_form_data_parserc C sl d| j krdS | jr8| j }|j| j | j| j| j}n| j| j | j f}| j }|\|d< |d< |d< dS )au Method used internally to retrieve submitted data. After calling
this sets `form` and `files` on the request object to multi dicts
filled with the incoming form data. As a matter of fact the input
stream will be empty afterwards. You can also call this method to
force the parsing of the form data.
.. versionadded:: 0.8
formNstreamfiles)
__dict__rP rU parse_get_stream_for_parsingmimetyperL Zmimetype_paramsrW rT )r0 parserdatadr2 r2 r3 _load_form_data s
zRequest._load_form_datac C s" t | dd}|dk r t|S | jS )zThis is the same as accessing :attr:`stream` with the difference
that if it finds cached data from calling :meth:`get_data` first it
will create a new stream out of the cached data.
.. versionadded:: 0.9.3
_cached_dataN)getattrr rW )r0 Z cached_datar2 r2 r3 r[ / s z Request._get_stream_for_parsingc C s2 | j jd}x t|pf D ]\}}|j qW dS )zCloses associated resources of this request object. This
closes all file handles explicitly. You can also use the request
object in a with statement which will automatically close it.
.. versionadded:: 0.9
rX N)rY r( r r: )r0 rX _keyvaluer2 r2 r3 r: ; s z
Request.closec C s | S )Nr2 )r0 r2 r2 r3 __enter__F s zRequest.__enter__c C s | j d S )N)r: )r0 exc_type exc_valuetbr2 r2 r3 __exit__I s zRequest.__exit__c C s | j rtdt| jS )a7
If the incoming form data was not encoded with a known mimetype
the data is stored unmodified in this stream for consumption. Most
of the time it is a better idea to use :attr:`data` which will give
you that data as a string. The stream only returns the data once.
Unlike :attr:`input_stream` this stream is properly guarded that you
can't accidentally read past the length of the input. Werkzeug will
internally always refer to this stream to read data which makes it
possible to wrap this object with a stream that does filtering.
.. versionchanged:: 0.9
This stream is now always available but might be consumed by the
form parser later on. Previously the stream was only set if no
parsing happened.
zXThis request was created with 'shallow=True', reading from the input stream is disabled.)r RuntimeErrorr r )r0 r2 r2 r3 rW L s zRequest.streamz
wsgi.inputzThe WSGI input stream.
In general it's a bad idea to use this one because you can
easily read past the boundary. Use the :attr:`stream`
instead.)docc C s | j ddS )z
Contains the incoming request data as string in case it came with
a mimetype Werkzeug does not handle.
T)parse_form_data)get_data)r0 r2 r2 r3 r^ o s z Request.datazte.Literal[False])cacheas_textrl r c C s d S )Nr2 )r0 rn ro rl r2 r2 r3 rm w s zRequest.get_data.zte.Literal[True]c C s d S )Nr2 )r0 rn ro rl r2 r2 r3 rm s c C sL t | dd}|dkr4|r | j | jj }|r4|| _|rH|j| j| j}|S )a This reads the buffered incoming data from the client into one
bytes object. By default this is cached but that behavior can be
changed by setting `cache` to `False`.
Usually it's a bad idea to call this method without checking the
content length first as a client could send dozens of megabytes or more
to cause memory problems on the server.
Note that if the form data was already parsed this method will not
return anything as form data parsing does not cache the data like
this method does. To implicitly invoke form data parsing function
set `parse_form_data` to `True`. When this is done the return value
of this method will be an empty string if the form parser handles
the data. This generally is not necessary as if the whole data is
cached (which is the default) the form parser will used the cached
data to parse the form data. Please be generally aware of checking
the content length first in any case before calling this method
to avoid exhausting server memory.
If `as_text` is set to `True` the return value will be a decoded
string.
.. versionadded:: 0.9
ra N)rb r` rW readra decoder) r* )r0 rn ro rl rvr2 r2 r3 rm s
z ImmutableMultiDict[str, str]c C s | j | jS )aD The form parameters. By default an
:class:`~werkzeug.datastructures.ImmutableMultiDict`
is returned from this function. This can be changed by setting
:attr:`parameter_storage_class` to a different type. This might
be necessary if the order of the form data is important.
Please keep in mind that file uploads will not end up here, but instead
in the :attr:`files` attribute.
.. versionchanged:: 0.9
Previous to Werkzeug 0.9 this would only contain form data for POST
and PUT requests.
)r` rV )r0 r2 r2 r3 rV s z Request.formzCombinedMultiDict[str, str]c C sT | j g}| jdkr |j| j g }x(|D ] }t|ts>t|}|j| q(W t|S )a A :class:`werkzeug.datastructures.CombinedMultiDict` that
combines :attr:`args` and :attr:`form`.
For GET requests, only ``args`` are present, not ``form``.
.. versionchanged:: 2.0
For GET requests, only ``args`` are present, not ``form``.
r )r4 r appendrV
isinstancer
r )r0 sourcesr4 r_ r2 r2 r3 values s
zRequest.valuesz$ImmutableMultiDict[str, FileStorage]c C s | j | jS )a :class:`~werkzeug.datastructures.MultiDict` object containing
all uploaded files. Each key in :attr:`files` is the name from the
````. Each value in :attr:`files` is a
Werkzeug :class:`~werkzeug.datastructures.FileStorage` object.
It basically behaves like a standard file object you know from Python,
with the difference that it also has a
:meth:`~werkzeug.datastructures.FileStorage.save` function that can
store the file on the filesystem.
Note that :attr:`files` will only contain data if the request method was
POST, PUT or PATCH and the ``