internal/tools/: webob-1.8.7 metadata and description

Homepage Simple index

WSGI request and response object

author Ian Bicking
  • Development Status :: 6 - Mature
  • Intended Audience :: Developers
  • License :: OSI Approved :: MIT License
  • Topic :: Internet :: WWW/HTTP :: WSGI
  • Topic :: Internet :: WWW/HTTP :: WSGI :: Application
  • Topic :: Internet :: WWW/HTTP :: WSGI :: Middleware
  • Programming Language :: Python :: 2.7
  • Programming Language :: Python :: 3.4
  • Programming Language :: Python :: 3.5
  • Programming Language :: Python :: 3.6
  • Programming Language :: Python :: 3.7
  • Programming Language :: Python :: Implementation :: CPython
  • Programming Language :: Python :: Implementation :: PyPy
keywords wsgi request web http
license MIT
maintainer Pylons Project
provides_extras docs
  • Sphinx >=1.7.5 ; extra == 'docs'
  • pylons-sphinx-themes ; extra == 'docs'
  • pytest >=3.1.0 ; extra == 'testing'
  • coverage ; extra == 'testing'
  • pytest-cov ; extra == 'testing'
  • pytest-xdist ; extra == 'testing'
requires_python >=2.7,!=3.0.*,!=3.1.*,!=3.2.*
File Tox results History
112 KB
Python Wheel
272 KB
Source Documentation Status

WebOb provides objects for HTTP requests and responses. Specifically it does this by wrapping the WSGI request environment and response status/headers/app_iter(body).

The request and response objects provide many conveniences for parsing HTTP request and forming HTTP responses. Both objects are read/write: as a result, WebOb is also a nice way to create HTTP requests and parse HTTP responses.

Support and Documentation

See the WebOb Documentation website to view documentation, report bugs, and obtain support.


WebOb is offered under the MIT-license.


WebOb was authored by Ian Bicking and is currently maintained by the Pylons Project and a team of contributors.

1.8.7 (2021-02-17)


  • Decoding deflate-encoded responses now supports data which is packed in a zlib container as it is supposed to be. The old, non-standard behaviour is still supported.


1.8.6 (2020-01-21)

Experimental Features

1.8.5 (2019-01-03)


  • Fixed one last remaining invalid escape sequence in a docstring.

1.8.4 (2018-11-11)



  • Some backslashes introduced with the new accept handling code were causing DeprecationWarnings upon compiling the source to pyc files, all of the backslashes have been reigned in as appropriate, and users should no longer see DeprecationWarnings for invalid escape sequence. See

1.8.3 (2018-10-14)


  • acceptparse.AcceptValidHeader, acceptparse.AcceptInvalidHeader, and acceptparse.AcceptNoHeader will now always ignore offers that do not match the required media type grammar when calling .acceptable_offers(). Previous versions raised a ValueError for invalid offers in AcceptValidHeader and returned them as acceptable in the others. See


  • Add Request.remote_host, exposing REMOTE_HOST environment variable.

  • Added acceptparse.Accept.parse_offer to codify what types of offers are compatible with acceptparse.AcceptValidHeader.acceptable_offers, acceptparse.AcceptMissingHeader.acceptable_offers, and acceptparse.AcceptInvalidHeader.acceptable_offers. This API also normalizes the offer with lowercased type/subtype and parameter names. See and

1.8.2 (2018-06-05)


1.8.1 (2018-04-10)


  • acceptparse.MIMEAccept which is deprecated in WebOb 1.8.0 made a backwards incompatible change that led to it raising on an invalid Accept header. This behaviour has now been reversed, as well as some other fixes to allow MIMEAccept to behave more like the old version. See

1.8.0 (2018-04-04)


  • request.POST now supports any requests with the appropriate Content-Type. Allowing any HTTP method to access form encoded content, including DELETE, PUT, and others. See


  • WebOb is no longer officially supported on Python 3.3 which was EOL’ed on 2017-09-29.

Backwards Incompatibilities

Experimental Features

These features are experimental and may change at any point in the future.


  • Exceptions now use string.Template.safe_substitute rather than string.Template.substitute. The latter would raise for missing mappings, the former will simply not substitute the missing variable. This is safer in case the WSGI environ does not contain the keys necessary for the body template. See

  • Request.host_url, Request.host_port, Request.domain correctly parse IPv6 Host headers as provided by a browser. See

  • Request.authorization would raise ValueError for unusual or malformed header values. See

  • Allow unnamed fields in form data to be properly transcoded when calling request.decode with an alternate encoding. See

  • Response.__init__ would discard app_iter when a Response had no body, this would cause issues when app_iter was an object that was tied to the life-cycle of a web application and had to be properly closed. app_iter is more advanced API for Response and thus even if it contains a body and is thus against the HTTP RFC’s, we should let the users shoot themselves by returning a body. See