./www/py-h11, Pure-Python, bring-your-own-I/O implementation of HTTP/1.1

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.8.1, Package name: py27-h11-0.8.1, Maintainer: pkgsrc-users

This is a little HTTP/1.1 library written from scratch in Python,
heavily inspired by hyper-h2.

It's a "bring-your-own-I/O" library; h11 contains no IO code
whatsoever. This means you can hook h11 up to your favorite network
API, and that could be anything you want: synchronous, threaded,
asynchronous, or your own implementation of RFC 6214 - h11 won't
judge you. (Compare this to the current state of the art, where
every time a new network API comes along then someone gets to start
over reimplementing the entire HTTP protocol from scratch.)


Required to run:
[devel/py-setuptools] [lang/python27]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: ec078eb027c5f0bfa93808e5d2b72478e067d398
RMD160: 925c8752788b45f979bc248a3c4232f431f740fc
Filesize: 91.806 KB

Version history: (Expand)


CVS history: (Expand)


   2018-05-14 10:05:12 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-h11: updated to 0.8.1

v0.8.1:

Bug fixes:
* Always return headers as bytes objects

Other changes:
* Added proper license notices to the Javascript used in our
  documentation
   2018-04-09 12:50:22 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-h11: updated to 0.8.0

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.
   2018-02-27 07:58:28 by Adam Ciarcinski | Files touched by this commit (1)
Log message:
Added "python" to CATEGORIES
   2018-02-26 13:06:13 by Leonardo Taccari | Files touched by this commit (4)
Log message:
py-h11: Import py-h11-0.7.0 as www/py-h11

This is a little HTTP/1.1 library written from scratch in Python,
heavily inspired by hyper-h2.

It's a "bring-your-own-I/O" library; h11 contains no IO code
whatsoever. This means you can hook h11 up to your favorite network
API, and that could be anything you want: synchronous, threaded,
asynchronous, or your own implementation of RFC 6214 - h11 won't
judge you. (Compare this to the current state of the art, where
every time a new network API comes along then someone gets to start
over reimplementing the entire HTTP protocol from scratch.)