Request / Response Objects

由 麦克马高 创建, 最后一次修改 2016-02-24

Request / Response Objects

The request and response objects wrap the WSGI environment or the returnvalue from a WSGI application so that it is another WSGI application(wraps a whole application).

How they Work

Your WSGI application is always passed two arguments. The WSGI “environment”and the WSGI start_response function that is used to start the responsephase. The Request class wraps the environ for easier access torequest variables (form data, request headers etc.).

The Response on the other hand is a standard WSGI application thatyou can create. The simple hello world in Werkzeug looks like this:

from werkzeug.wrappers import Response
application = Response('Hello World!')

To make it more useful you can replace it with a function and do someprocessing:

from werkzeug.wrappers import Request, Response

def application(environ, start_response):
    request = Request(environ)
    response = Response("Hello %s!" % request.args.get('name', 'World!'))
    return response(environ, start_response)

Because this is a very common task the Request object providesa helper for that. The above code can be rewritten like this:

from werkzeug.wrappers import Request, Response

def application(request):
    return Response("Hello %s!" % request.args.get('name', 'World!'))

The application is still a valid WSGI application that accepts theenvironment and start_response callable.

Mutability and Reusability of Wrappers

The implementation of the Werkzeug request and response objects are tryingto guard you from common pitfalls by disallowing certain things as much aspossible. This serves two purposes: high performance and avoiding ofpitfalls.

For the request object the following rules apply:

  1. The request object is immutable. Modifications are not supported bydefault, you may however replace the immutable attributes with mutableattributes if you need to modify it.
  2. The request object may be shared in the same thread, but is not threadsafe itself. If you need to access it from multiple threads, uselocks around calls.
  3. It's not possible to pickle the request object.

For the response object the following rules apply:

  1. The response object is mutable
  2. The response object can be pickled or copied after freeze() wascalled.
  3. Since Werkzeug 0.6 it's safe to use the same response object formultiple WSGI responses.
  4. It's possible to create copies using copy.deepcopy.

Base Wrappers

These objects implement a common set of operations. They are missing fancyaddon functionality like user agent parsing or etag handling. These featuresare available by mixing in various mixin classes or using Request andResponse.

class werkzeug.wrappers.BaseRequest(environ, populate_request=True, shallow=False)
Very basic request object. This does not implement advanced stuff likeentity tag parsing or cache controls. The request object is created withthe WSGI environment as first argument and will add itself to the WSGIenvironment as 'werkzeug.request' unless it's created withpopulate_request set to False.

There are a couple of mixins available that add additional functionalityto the request object, there is also a class called Request whichsubclasses BaseRequest and all the important mixins.

It's a good idea to create a custom subclass of the BaseRequestand add missing functionality either via mixins or direct implementation.Here an example for such subclasses:

from werkzeug.wrappers import BaseRequest, ETagRequestMixin

class Request(BaseRequest, ETagRequestMixin):

Request objects are read only. As of 0.5 modifications are notallowed in any place. Unlike the lower level parsing functions therequest object will use immutable objects everywhere possible.

Per default the request object will assume all the text data is utf-8encoded. Please refer to the unicode chapter for moredetails about customizing the behavior.

Per default the request object will be added to the WSGIenvironment as werkzeug.request to support the debugging system.If you don't want that, set populate_request to False.

If shallow is True the environment is initialized as shallowobject around the environ. Every operation that would modify theenviron in any way (such as consuming form data) raises an exceptionunless the shallow attribute is explicitly set to False. Thisis useful for middlewares where you don't want to consume the formdata by accident. A shallow request is not populated to the WSGIenvironment.

在 0.5 版更改: read-only mode was enforced by using immutables classes for alldata.

The WSGI environment that the request object uses for data retrival.

True if this request object is shallow (does not modify environ),False otherwise.

_get_file_stream(total_content_length, content_type, filename=None, content_length=None)
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 totalcontent length is higher than 500KB. Because many browsers do notprovide a content length for the files only the total contentlength matters.

  • total_content_length – the total content length of all thedata in the request combined. This valueis guaranteed to be there.
  • content_type – the mimetype of the uploaded file.
  • filename – the filename of the uploaded file. May be None.
  • content_length – the length of this file. This value is usuallynot provided because webbrowsers do not providethis value.

If a forwarded header exists this is a list of all ip addressesfrom the client ip to the last proxy server.

classmethod application(f)
Decorate a function as responder that accepts the request as firstargument. This works like the responder() decorator but thefunction is passed the request object as first argument and therequest object will be closed automatically:

def my_wsgi_app(request):
    return Response('Hello World!')
参数: f – the WSGI callable to decorate
返回: a new WSGI callable

The parsed URL parameters. By default anImmutableMultiDictis returned from this function. This can be changed by settingparameter_storage_class to a different type. This mightbe necessary if the order of the form data is important.

Like url but without the querystring

charset = 'utf-8'
the charset for the request, defaults to utf-8

Closes associated resources of this request object. Thiscloses all file handles explicitly. You can also use the requestobject in a with statement with will automatically close it.

0.9 新版功能.

Read only access to the retrieved cookie values as dictionary.

the type to be used for dict values from the incoming WSGI environment.By default anImmutableTypeConversionDict is used(for example for cookies).

0.6 新版功能.

ImmutableTypeConversionDict 的别名

disable_data_descriptor = False
Indicates weather the data descriptor should be allowed to read andbuffer up the input stream. By default it's enabled.

0.9 新版功能.

encoding_errors = 'replace'
the error handling procedure for errors, defaults to ‘replace'

MultiDict object containingall uploaded files. Each key in files is the name from the. Each value in files is aWerkzeug FileStorage object.

Note that files will only contain data if the request method wasPOST, PUT or PATCH and the

that posted to the request hadenctype="multipart/form-data". It will be empty otherwise.

See the MultiDict /FileStorage documentation formore details about the used data structure.

The form parameters. By default anImmutableMultiDictis returned from this function. This can be changed by settingparameter_storage_class to a different type. This mightbe necessary if the order of the form data is important.

The form data parser that shoud be used. Can be replaced to customizethe form date parsing.

FormDataParser 的别名

classmethod from_values(args, kwargs*)
Create a new request object based on the values provided. Ifenviron is given missing values are filled from there. This method isuseful for small scripts when you need to simulate a request from an URL.Do not use this method for unittesting, there is a full featured clientobject (Client) that allows to create multipart requests,support for cookies etc.

This accepts the same options as theEnvironBuilder.

在 0.5 版更改: This method now accepts the same arguments asEnvironBuilder. Because of this theenviron parameter is now called environ_overrides.

Requested path as unicode, including the query string.

get_data(cache=True, as_text=False, parse_form_data=False)
This reads the buffered incoming data from the client into onebytestring. By default this is cached but that behavior can bechanged by setting cache to False.

Usually it's a bad idea to call this method without checking thecontent length first as a client could send dozens of megabytes or moreto cause memory problems on the server.

Note that if the form data was already parsed this method will notreturn anything as form data parsing does not cache the data likethis method does. To implicitly invoke form data parsing functionset parse_form_data to True. When this is done the return valueof this method will be an empty string if the form parser handlesthe data. This generally is not necessary as if the whole data iscached (which is the default) the form parser will used the cacheddata to parse the form data. Please be generally aware of checkingthe content length first in any case before calling this methodto avoid exhausting server memory.

If as_text is set to True the return value will be a decodedunicode string.

0.9 新版功能.

The headers from the WSGI environ as immutableEnvironHeaders.

Just the host including the port if available.

Just the host with scheme.

boolean that is True if the application is served bya WSGI server that spawns multiple processes.

boolean that is True if the application is served bya multithreaded WSGI server.

boolean that is True if the application will be executed onlyonce in a process lifetime. This is the case for CGI for example,but it's not guaranteed that the exeuction only happens one time.

True if the request is secure.

True if the request was triggered via a JavaScript XMLHttpRequest.This only works with libraries that support the X-Requested-Withheader and set it to “XMLHttpRequest”. Libraries that do that areprototype, jQuery and Mochikit and probably some more.

the type to be used for list values from the incoming WSGI environment.By default an ImmutableList is used(for example for access_list).

0.6 新版功能.

ImmutableList 的别名

Creates the form data parser. Instanciates theform_data_parser_class with some parameters.

0.8 新版功能.

max_content_length = None
the maximum content length. This is forwarded to the form dataparsing function (parse_form_data()). When set and theform or files attribute is accessed and theparsing fails because more than the specified value is transmitteda RequestEntityTooLarge exception is raised.

Have a look at Dealing with Request Data for more details.

0.5 新版功能.

max_form_memory_size = None
the maximum form field size. This is forwarded to the form dataparsing function (parse_form_data()). When set and theform or files attribute is accessed and thedata in memory for post data is longer than the specified value aRequestEntityTooLarge exception is raised.

Have a look at Dealing with Request Data for more details.

0.5 新版功能.

The transmission method. (For example 'GET' or 'POST').

the class to use for args and form. The default is anImmutableMultiDict which supportsmultiple values per key. alternatively it makes sense to use anImmutableOrderedMultiDict whichpreserves order or a ImmutableDictwhich is the fastest but only remembers the last key. It is alsopossible to use mutable structures, but this is not recommended.

0.6 新版功能.

ImmutableMultiDict 的别名

Requested path as unicode. This works a bit like the regular pathinfo in the WSGI environment but will always include a leading slash,even if the URL root is accessed.

The URL parameters as raw bytestring.

The remote address of the client.

If the server supports user authentication, and the script isprotected, this attribute contains the username the user hasauthenticated as.

URL scheme (http or https).

0.7 新版功能.

The root path of the script without the trailing slash.

The stream to read incoming data from. Unlike input_streamthis stream is properly guarded that you can't accidentally read pastthe length of the input. Werkzeug will internally always refer tothis stream to read data which makes it possible to wrap thisobject with a stream that does filtering.

在 0.9 版更改: This stream is now always available but might be consumed by theform parser later on. Previously the stream was only set if noparsing happened.

trusted_hosts = None
Optionally a list of hosts that is trusted by this request. By defaultall hosts are trusted which means that whatever the client sends thehost is will be accepted. This is the recommended setup as a webservershould manually be set up to not route invalid hosts to the application.

0.9 新版功能.

The reconstructed current URL

The charset that is assumed for URLs. Defaults to the valueof charset.

0.6 新版功能.

The full URL root (with hostname), this is the application root.

Combined multi dict for args and form.

Returns True if the request method carries content. As ofWerkzeug 0.9 this will be the case if a content type is transmitted.

0.8 新版功能.

class werkzeug.wrappers.BaseResponse(response=None, status=None, headers=None, mimetype=None, content_type=None, direct_passthrough=False)
Base response class. The most important fact about a response objectis that it's a regular WSGI application. It's initialized with a coupleof response parameters (headers, body, status code etc.) and will start avalid WSGI response when called with the environ and start responsecallable.

Because it's a WSGI application itself processing usually ends before theactual response is sent to the server. This helps debugging systemsbecause they can catch all the exceptions before responses are started.

Here a small example WSGI application that takes advantage of theresponse objects:

from werkzeug.wrappers import BaseResponse as Response

def index():
    return Response('Index page')

def application(environ, start_response):
    path = environ.get('PATH_INFO') or '/'
    if path == '/':
        response = index()
        response = Response('Not Found', status=404)
    return response(environ, start_response)

Like BaseRequest which object is lacking a lot of functionalityimplemented in mixins. This gives you a better control about the actualAPI of your response objects, so you can create subclasses and add customfunctionality. A full featured response object is available asResponse which implements a couple of useful mixins.

To enforce a new type of already existing responses you can use theforce_type() method. This is useful if you're working with differentsubclasses of response objects and you want to post process them with aknow interface.

Per default the request object will assume all the text data is utf-8encoded. Please refer to the unicode chapter for moredetails about customizing the behavior.

Response can be any kind of iterable or string. If it's a string it'sconsidered being an iterable with one item which is the string passed.Headers can be a list of tuples or aHeaders object.

Special note for mimetype and content_type: For most mime typesmimetype and content_type work the same, the difference affectsonly ‘text' mimetypes. If the mimetype passed with mimetype is amimetype starting with text/, the charset parameter of the responseobject is appended to it. In contrast the content_type parameter isalways added as header unmodified.

在 0.5 版更改: the direct_passthrough parameter was added.

  • response – a string or response iterable.
  • status – a string with a status or an integer with the status code.
  • headers – a list of headers or aHeaders object.
  • mimetype – the mimetype for the request. See notice above.
  • content_type – the content type for the request. See notice above.
  • direct_passthrough – if set to True iter_encoded() is notcalled before iteration which makes itpossible to pass special iterators thoughunchanged (see wrap_file() for moredetails.)

The application iterator. If constructed from a string this will be alist, otherwise the object provided as application iterator. (The firstargument passed to BaseResponse)

A Headers object representing the response headers.

The response status as integer.

If direct_passthrough=True was passed to the response object or ifthis attribute was set to True before using the response object asWSGI application, the wrapped iterator is returned unchanged. Thismakes it possible to pass a special wsgi.file_wrapper to the responseobject. See wrap_file() for more details.

call(environ, start_response)
Process this response as WSGI application.

  • environ – the WSGI environment.
  • start_response – the response callable provided by the WSGIserver.

an application iterator

This method can be called by methods that need a sequence. Ifmutable is true, it will also ensure that the response sequenceis a standard Python list.

0.6 新版功能.

autocorrect_location_header = True
Should this response object correct the location header to be RFCconformant? This is true by default.

0.8 新版功能.

automatically_set_content_length = True
Should this response object automatically set the content-lengthheader if possible? This is true by default.

0.8 新版功能.

Returns the content length if available or None otherwise.

Adds a function to the internal list of functions that shouldbe called as part of closing down the response. Since 0.7 thisfunction also returns the function that was passed so that thiscan be used as a decorator.

0.6 新版功能.

charset = 'utf-8'
the charset of the response.

Close the wrapped response if possible. You can also use the objectin a with statement which will automatically close it.

0.9 新版功能: Can now be used in a with statement.

A descriptor that calls get_data() and set_data(). Thisshould not be used and will eventually get deprecated.

default_mimetype = 'text/plain'
the default mimetype if none is provided.

default_status = 200
the default status if none is provided.

delete_cookie(key, path='/', domain=None)
Delete a cookie. Fails silently if key doesn't exist.

  • key – the key (name) of the cookie to be deleted.
  • path – if the cookie that should be deleted was limited to apath, the path has to be defined here.
  • domain – if the cookie that should be deleted was limited to adomain, that domain has to be defined here.

classmethod force_type(response, environ=None)
Enforce that the WSGI response is a response object of the currenttype. Werkzeug will use the BaseResponse internally in manysituations like the exceptions. If you call get_response() on anexception you will get back a regular BaseResponse object, evenif you are using a custom subclass.

This method can enforce a given response type, and it will alsoconvert arbitrary WSGI callables into response objects if an environis provided:

# convert a Werkzeug response object into an instance of the
# MyResponseClass subclass.
response = MyResponseClass.force_type(response)

# convert any WSGI application into a response object
response = MyResponseClass.force_type(response, environ)

This is especially useful if you want to post-process responses inthe main dispatcher and use functionality provided by your subclass.

Keep in mind that this will modify response objects in place ifpossible!

  • response – a response object or wsgi application.
  • environ – a WSGI environment object.

a response object.

Call this method if you want to make your response object ready forbeing pickled. This buffers the generator if there is one. It willalso set the Content-Length header to the length of the body.

在 0.6 版更改: The Content-Length header is now set.

classmethod from_app(app, environ, buffered=False)
Create a new response object from an application output. Thisworks best if you pass it an application that returns a generator allthe time. Sometimes applications may use the write() callablereturned by the start_response function. This tries to resolve suchedge cases automatically. But if you don't get the expected outputyou should set buffered to True which enforces buffering.

  • app – the WSGI application to execute.
  • environ – the WSGI environment to execute against.
  • buffered – set to True to enforce buffering.

a response object.

Returns the application iterator for the given environ. Dependingon the request method and the current status code the return valuemight be an empty response rather than the one from the response.

If the request method is HEAD or the status code is in a rangewhere the HTTP specification requires an empty response, an emptyiterable is returned.

0.6 新版功能.

参数: environ – the WSGI environment of the request.
返回: a response iterable.

The string representation of the request body. Whenever you callthis property the request iterable is encoded and flattened. Thiscan lead to unwanted behavior if you stream big data.

This behavior can be disabled by settingimplicit_sequence_conversion to False.

If as_text is set to True the return value will be a decodedunicode string.

0.9 新版功能.

This is automatically called right before the response is startedand returns headers modified for the given environment. It returns acopy of the headers from the response with some modifications appliedif necessary.

For example the location header (if present) is joined with the rootURL of the environment. Also the content length is automatically setto zero here for certain status codes.

在 0.6 版更改: Previously that function was called fix_headers and modifiedthe response object in place. Also since 0.6, IRIs in locationand content-location headers are handled properly.

Also starting with 0.6, Werkzeug will attempt to set the contentlength if it is able to figure it out on its own. This is thecase if all the strings in the response iterable are alreadyencoded and the iterable is buffered.

参数: environ – the WSGI environment of the request.
返回: returns a new Headersobject.

Returns the final WSGI response as tuple. The first item inthe tuple is the application iterator, the second the status andthe third the list of headers. The response returned is createdspecially for the given environment. For example if the requestmethod in the WSGI environment is 'HEAD' the response willbe empty and only the headers and status code will be present.

0.6 新版功能.

参数: environ – the WSGI environment of the request.
返回: an (app_iter,status,headers) tuple.

implicit_sequence_conversion = True
if set to False accessing properties on the response object willnot try to consume the response iterator and convert it into a list.

0.6.2 新版功能: That attribute was previously called implicit_seqence_conversion.(Notice the typo). If you did use this feature, you have to adaptyour code to the name change.

If the iterator is buffered, this property will be True. Aresponse object will consider an iterator to be buffered if theresponse attribute is a list or tuple.

0.6 新版功能.

If the response is streamed (the response is not an iterable witha length information) this property is True. In this case streamedmeans that there is no information about the number of iterations.This is usually True if a generator is passed to the response object.

This is useful for checking before applying some sort of postfiltering that should not take place for streamed responses.

Iter the response encoded with the encoding of the response.If the response object is invoked as WSGI application the returnvalue of this method is used as application iterator unlessdirect_passthrough was activated.

Converts the response iterator in a list. By default this happensautomatically if required. If implicit_sequence_conversion isdisabled, this method is not automatically called and some propertiesmight raise exceptions. This also encodes all the items.

0.6 新版功能.

set_cookie(key, value='', max_age=None, expires=None, path='/', domain=None, secure=None, httponly=False)
Sets a cookie. The parameters are the same as in the cookie Morselobject in the Python standard library but it accepts unicode data, too.

  • key – the key (name) of the cookie to be set.
  • value – the value of the cookie.
  • max_age – should be a number of seconds, or None (default) ifthe cookie should last only as long as the client'sbrowser session.
  • expires – should be a datetime object or UNIX timestamp.
  • domain – if you want to set a cross-domain cookie. For example,domain="" will set a cookie that isreadable by the domain, etc. Otherwise, a cookie will onlybe readable by the domain that set it.
  • path – limits the cookie to a given