/usr/share/doc/python-werkzeug-doc/html/_sources/http.txt is in python-werkzeug-doc 0.9.4+dfsg-1.1ubuntu2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 | ==============
HTTP Utilities
==============
.. module:: werkzeug.http
Werkzeug provides a couple of functions to parse and generate HTTP headers
that are useful when implementing WSGI middlewares or whenever you are
operating on a lower level layer. All this functionality is also exposed
from request and response objects.
Date Functions
==============
The following functions simplify working with times in an HTTP context.
Werkzeug uses offset-naive :class:`~datetime.datetime` objects internally
that store the time in UTC. If you're working with timezones in your
application make sure to replace the tzinfo attribute with a UTC timezone
information before processing the values.
.. autofunction:: cookie_date
.. autofunction:: http_date
.. autofunction:: parse_date
Header Parsing
==============
The following functions can be used to parse incoming HTTP headers.
Because Python does not provide data structures with the semantics required
by :rfc:`2616`, Werkzeug implements some custom data structures that are
:ref:`documented separately <http-datastructures>`.
.. autofunction:: parse_options_header
.. autofunction:: parse_set_header
.. autofunction:: parse_list_header
.. autofunction:: parse_dict_header
.. autofunction:: parse_accept_header(value, [class])
.. autofunction:: parse_cache_control_header
.. autofunction:: parse_authorization_header
.. autofunction:: parse_www_authenticate_header
.. autofunction:: parse_if_range_header
.. autofunction:: parse_range_header
.. autofunction:: parse_content_range_header
Header Utilities
================
The following utilities operate on HTTP headers well but do not parse
them. They are useful if you're dealing with conditional responses or if
you want to proxy arbitrary requests but want to remove WSGI-unsupported
hop-by-hop headers. Also there is a function to create HTTP header
strings from the parsed data.
.. autofunction:: is_entity_header
.. autofunction:: is_hop_by_hop_header
.. autofunction:: remove_entity_headers
.. autofunction:: remove_hop_by_hop_headers
.. autofunction:: is_byte_range_valid
.. autofunction:: quote_header_value
.. autofunction:: unquote_header_value
.. autofunction:: dump_header
Cookies
=======
.. autofunction:: parse_cookie
.. autofunction:: dump_cookie
Conditional Response Helpers
============================
For conditional responses the following functions might be useful:
.. autofunction:: parse_etags
.. autofunction:: quote_etag
.. autofunction:: unquote_etag
.. autofunction:: generate_etag
.. autofunction:: is_resource_modified
Constants
=========
.. data:: HTTP_STATUS_CODES
A dict of status code -> default status message pairs. This is used
by the wrappers and other places where an integer status code is expanded
to a string throughout Werkzeug.
Form Data Parsing
=================
.. module:: werkzeug.formparser
Werkzeug provides the form parsing functions separately from the request
object so that you can access form data from a plain WSGI environment.
The following formats are currently supported by the form data parser:
- `application/x-www-form-urlencoded`
- `multipart/form-data`
Nested multipart is not currently supported (Werkzeug 0.9), but it isn't used
by any of the modern web browsers.
Usage example:
>>> from cStringIO import StringIO
>>> data = '--foo\r\nContent-Disposition: form-data; name="test"\r\n' \
... '\r\nHello World!\r\n--foo--'
>>> environ = {'wsgi.input': StringIO(data), 'CONTENT_LENGTH': str(len(data)),
... 'CONTENT_TYPE': 'multipart/form-data; boundary=foo',
... 'REQUEST_METHOD': 'POST'}
>>> stream, form, files = parse_form_data(environ)
>>> stream.read()
''
>>> form['test']
u'Hello World!'
>>> not files
True
Normally the WSGI environment is provided by the WSGI gateway with the
incoming data as part of it. If you want to generate such fake-WSGI
environments for unittesting you might want to use the
:func:`create_environ` function or the :class:`EnvironBuilder` instead.
.. autoclass:: FormDataParser
.. autofunction:: parse_form_data
.. autofunction:: parse_multipart_headers
|