v0.8.0: Backwards incompatible changes: h11 now performs stricter validation on outgoing header names and header values: illegal characters are now rejected (example: you can't put a newline into an HTTP header), and header values with leading/trailing whitespace are also rejected (previously h11 would silently discard the whitespace). All these checks were already performed on incoming headers; this just extends that to outgoing headers. New features: New method :meth:Connection.send_failed, to notify a :class:Connection object when data returned from :meth:Connection.send was not sent. Bug fixes: Make sure that when computing the framing headers for HEAD responses, we produce the same results as we would for the corresponding GET. Error out if a request has multiple Host: headers. Send the Host: header first, as recommended by RFC 7230. The Expect: header is case-insensitive, so use case-insensitive matching when looking for 100-continue. Other changes: Better error messages in several cases. Provide correct error_status_hint in exception raised when encountering an invalid Transfer-Encoding header. For better compatibility with broken servers, h11 now tolerates responses where the reason phrase is missing (not just empty). Various optimizations and documentation improvements.
6 lines
387 B
Text
6 lines
387 B
Text
$NetBSD: distinfo,v 1.2 2018/04/09 10:50:22 adam Exp $
|
|
|
|
SHA1 (h11-0.8.0.tar.gz) = 2c4ef9c92e02263899eeeb4cc658b5b084ba7457
|
|
RMD160 (h11-0.8.0.tar.gz) = 78f16e2bd68f97165cc07b43bc32bef9f74a5eb6
|
|
SHA512 (h11-0.8.0.tar.gz) = edd440dd74c03ce4fb7fd9e6b88e7c9550eb7c50b70676b506a8dafaf1469d9830de01300536128f0e7c61ae09d5256d15875dd5e6a9b99b89470bf70ee343b8
|
|
Size (h11-0.8.0.tar.gz) = 92722 bytes
|