Commit graph

15 commits

Author SHA1 Message Date
adam
3d67758b4d py-daphne: updated to 2.2.5
2.2.5:
* WebSocket handshakes are now affected by the websocket connect timeout, so
  you can limit them from the command line.
* Server name can now be set using --server-name
2019-02-13 15:55:41 +00:00
adam
698df918c8 py-daphne: updated to 2.2.4
2.2.4:
* No longer listens on port 8000 when a file descriptor is provided with --fixed
* Fixed a memory leak with WebSockets
2018-12-16 18:22:59 +00:00
adam
9680d0585a py-daphne: updated to 2.2.3
2.2.3:

* Enforce that response headers are only bytestrings, rather than allowing
  unicode strings and coercing them into bytes.

* New command-line options to set proxy header names: --proxy-headers-host and
  --proxy-headers-port.
2018-11-28 14:35:29 +00:00
adam
1440f5e20c py-daphne: updated to 2.2.2
2.2.2:
* X-Forwarded-Proto support is now present and enabled if you turn on the
  --proxy-headers flag
* ASGI applications are no longer instantiated in a thread (the ASGI spec
  was finalised to say all constructors must be non-blocking on the main thread)

2.2.1:
* Python 3.7 compatability is flagged and ensured by using Twisted 18.7 and
  above as a dependency.
* The send() awaitable in applications no longer blocks if the connection is
  closed.
* Fixed a race condition where applications would be cleaned up before they
  had even started.
2018-08-19 10:53:11 +00:00
adam
add318758a py-daphne: updated to 2.2.0
2.2.0:

* HTTP timeouts have been removed by default, as they were only needed
  with ASGI/Channels 1. You can re-enable them with the --http-timeout
  argument to Daphne.

* Occasional errors on application timeout for non-fully-opened sockets
  and for trying to read closed requests under high load are fixed.

* X-Forwarded-For headers are now correctly decoded in all environments
  and no longer have unicode matching issues.
2018-06-14 07:55:00 +00:00
adam
0eec37403f py-daphne: updated to 2.1.1
2.1.1:
* ASGI application constructors are now run in a threadpool as they might
  contain blocking synchronous code.
2018-04-30 07:36:13 +00:00
joerg
cce979361d Simplify 2018-03-26 00:30:50 +00:00
joerg
b3e0c91fb9 Needs py-test-runner. 2018-03-24 17:07:06 +00:00
adam
fbe79a8166 py-daphne: updated to 2.1.0
2.1.0:
* Removed subprotocol support from server, as it never really worked. Subprotocols
  can instead be negotiated by ASGI applications now.
* Non-ASCII query strings now raise a 400 Bad Request error rather than silently
  breaking the logger
2018-03-14 08:00:08 +00:00
adam
ac4c906aee py-daphne: updated to 2.0.4
2.0.4:
* Ping timeouts no longer reset on outgoing data, only incoming data
* No more errors when connections close prematurely
2018-02-22 08:54:28 +00:00
adam
9aa9f02f23 py-daphne: updated to 2.0.3
2.0.3:
* Unix socket listening no longer errors during startup (introduced in 2.0.2)
* ASGI Applications are now not immediately killed on disconnection but instead
  given --application-close-timeout seconds to exit (defaults to 10)

2.0.2:
* WebSockets are no longer closed after the duration of http_timeout

2.0.1:
* Updated logging to correctly route exceptions through the main Daphne logger

2.0.0:
* Major rewrite to the new async-based ASGI specification and to support
  Channels 2. Not backwards compatible.
2018-02-14 14:21:33 +00:00
adam
ab37ab3ca0 py-daphne: updated to 1.4.2
1.4.2:
* Bugfix for WebSocket protocol when X-Forwarded-For is turned on.

1.4.1:
* Bugfix for a bad merge of HTTPFactory for X-Forwarded-Proto causing Daphne
  to not start.

1.4.0:
* The X-Forwarded-Proto header can now be used to pass along protocol from
  a reverse proxy.
* WebSocket headers are now correctly always passed as bytestrings.
2018-01-10 08:36:54 +00:00
joerg
6e56f72628 Restrict Python support as py-asgiref doesn't support 2.7 and 3.4. 2017-12-08 20:38:59 +00:00
wiz
5d86518619 Switch github HOMEPAGEs to https. 2017-07-30 22:32:10 +00:00
adam
fa27570c64 Daphne is a HTTP, HTTP2 and WebSocket protocol server for ASGI, and developed
to power Django Channels.

It supports automatic negotiation of protocols; there's no need for URL
prefixing to determine WebSocket endpoints versus HTTP endpoints.
2017-06-21 19:09:21 +00:00