Update waitress to 1.1.0

[pyup-bot]

There's a new version of waitress available.
You are currently using 0.8.9. I have updated it to 1.1.0

These links might come in handy: PyPI | Changelog | Repo

Changelog

1.1.0

---

Features

• Waitress now has a main and thus may be called with python -mwaitress

Bugfixes

• Waitress no longer allows lowercase HTTP verbs. This change was made to fall
  in line with most HTTP servers. See No longer allow lowercase HTTP methods Pylons/waitress#170

• When receiving non-ascii bytes in the request URL, waitress will no longer
  abruptly close the connection, instead returning a 400 Bad Request. See
  Fix issue #64 Uncaptured exception instead of 400 when receiving non-ascii bytes in request url Pylons/waitress#162 and
  Uncaptured exception instead of 400 when receiving non-ascii bytes in request url Pylons/waitress#64

1.0.2

---

Features

• Python 3.6 is now officially supported in Waitress

Bugfixes

• Add a work-around for libc issue on Linux not following the documented
  standards. If getnameinfo() fails because of DNS not being available it
  should return the IP address instead of the reverse DNS entry, however
  instead getnameinfo() raises. We catch this, and ask getnameinfo()
  for the same information again, explicitly asking for IP address instead of
  reverse DNS hostname. See waitress 1.0 doesn't work on linux without reachable DNS Pylons/waitress#149 and
  Add fallback to numeric only nameinfo Pylons/waitress#153

1.0.1

---

Bugfixes

• IPv6 support on Windows was broken due to missing constants in the socket
  module. This has been resolved by setting the constants on Windows if they
  are missing. See socket.IPPROTO_IPV6 undefined in Python 2.7.12 for Windows Pylons/waitress#138

• A ValueError was raised on Windows when passing a string for the port, on
  Windows in Python 2 using service names instead of port numbers doesn't work
  with getaddrinfo. This has been resolved by attempting to convert the port
  number to an integer, if that fails a ValueError will be raised. See
  Invalid host/port specified error on Windows Pylons/waitress#139

1.0.0

---

Bugfixes

• Removed AI_ADDRCONFIG from the call to getaddrinfo, this resolves an
  issue whereby getaddrinfo wouldn't return any addresses to bind to on
  hosts where there is no internet connection but localhost is requested to be
  bound to. See waitress 1.0a1 doesn't work on linux without internet connectivity (DNS?) Pylons/waitress#131 for more
  information.

Deprecations

• Python 2.6 is no longer supported.

Features

• IPv6 support

• Waitress is now able to listen on multiple sockets, including IPv4 and IPv6.
  Instead of passing in a host/port combination you now provide waitress with a
  space delineated list, and it will create as many sockets as required.

.. code-block:: python

from waitress import serve
serve(wsgiapp, listen='0.0.0.0:8080 [::]:9090 *:6543')

Security

• Waitress will now drop HTTP headers that contain an underscore in the key
  when received from a client. This is to stop any possible underscore/dash
  conflation that may lead to security issues. See
  Prevent header spoofing via underscore/dash conflation. Pylons/waitress#80 and
  https://www.djangoproject.com/weblog/2015/jan/13/security/

0.9.0

---

Deprecations

• Python 3.2 is no longer supported by Waitress.

• Python 2.6 will no longer be supported by Waitress in future releases.

Security/Protections

• Building on the changes made in pull request 117, add in checking for line
  feed/carriage return HTTP Response Splitting in the status line, as well as
  the key of a header. See Check header names and status for line feed/carriage return. Fixes #122 Pylons/waitress#124 and
  HTTP Response Splitting - Status/Header Names Pylons/waitress#122.

• Waitress will no longer accept headers or status lines with
  newline/carriage returns in them, thereby disallowing HTTP Response
  Splitting. See HTTP Response Splitting Pylons/waitress#117 for
  more information, as well as
  https://www.owasp.org/index.php/HTTP_Response_Splitting.

Bugfixes

• FileBasedBuffer and more important ReadOnlyFileBasedBuffer no longer report
  False when tested with bool(), instead always returning True, and becoming
  more iterator like.
  See: Fix FileBasedBuffer (and ReadOnlyFileBasedBuffer) to act more like iterators Pylons/waitress#82 and
  Nested Bottle app with Waitress Pylons/waitress#76

• Call prune() on the output buffer at the end of a request so that it doesn't
  continue to grow without bounds. See
  Memory keeps increasing when user request data whose size < 1M (outbuf_overflow default ) Pylons/waitress#111 for more information.

0.8.10

---

• Add support for Python 3.4, 3.5b2, and PyPy3.

• Use a nonglobal asyncore socket map by default, trying to prevent conflicts
  with apps and libs that use the asyncore global socket map ala
  Error with cassandra Pylons/waitress#63. You can get the old
  use-global-socket-map behavior back by passing asyncore.socket_map to the
  create_server function as the map argument.

• Waitress violated PEP 3333 with respect to reraising an exception when
  start_response was called with an exc_info argument. It would
  reraise the exception even if no data had been sent to the client. It now
  only reraises the exception if data has actually been sent to the client.
  See Fix: start_response() should only re-raise exc_info if headers have been written Pylons/waitress#52 and
  start_response() reraises exc_info even if headers have not been sent Pylons/waitress#51

• Add a docs section to tox.ini that, when run, ensures docs can be built.

• If an application value of None is supplied to the create_server
  constructor function, a ValueError is now raised eagerly instead of an error
  occuring during runtime. See Waitress needs clear error message on no WSGI app Pylons/waitress#60

• Fix parsing of multi-line (folded) headers.
  See multi-line (folded) HTTP header wrongly parsed Pylons/waitress#53 and
  Fix multi line header parsing Pylons/waitress#90

• Switch from the low level Python thread/_thread module to the threading
  module.

• Improved exception information should module import go awry.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖