[issue20188] ALPN support for TLS

Mark Nottingham added the comment: HTTP/2 requires ALPN, BTW. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20188 ___ ___ Python-bugs-list

[issue21308] PEP 466: backport ssl changes

Changes by Mark Nottingham m...@mnot.net: -- nosy: +mnot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21308 ___ ___ Python-bugs-list mailing list

[issue5639] Support TLS SNI extension in ssl module

Mark Nottingham added the comment: This is *not* a feature request, it's a bug fix in the underlying protocols. Client sides that do not send SNI are actively hurting the Web and the Internet by constraining the deployment of TLS. The closest analogy would be if Python's HTTP client side

[issue20188] ALPN support for TLS

New submission from Mark Nottingham: In #14204, support for NPN was added. Subsequently, NPN has been superseded by ALPN in the IETF, and support for it is coming in OpenSSL 1.0.2. http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg http://rt.openssl.org/Ticket/Display.html?id=3073 http

[issue8885] markupbase declaration errors aren't recoverable

Mark Nottingham m...@mnot.net added the comment: Why remove 2.7? It'd be an easy bug fix if j is incremented. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8885

[issue7827] recv_into() argument 1 must be pinned buffer, not bytearray

Mark Nottingham m...@mnot.net added the comment: Seems to be fixed in 2.7, although I'm not sure when exactly : Python 2.7.2 (default, Oct 21 2011, 22:13:39) [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin Type help, copyright, credits or license for more

[issue7827] recv_into() argument 1 must be pinned buffer, not bytearray

Mark Nottingham m...@mnot.net added the comment: From the release notes, perhaps it was #8104. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7827

[issue7097] urlparse.urljoin of simple http:// and somedomain.com produces incorrect result

Mark Nottingham m...@mnot.net added the comment: http: and http:// are both valid base URIs; see RFC3986. More to the point, it's a useful thing to use a scheme as a base URI; many users omit the HTTP:// from their URIs. -- nosy: +mnot ___ Python

[issue7827] recv_into() argument 1 must be pinned buffer, not bytearray

Changes by Mark Nottingham m...@mnot.net: -- nosy: +mnot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7827 ___ ___ Python-bugs-list mailing list

[issue8885] markerbase declaration errors aren't recoverable

Mark Nottingham m...@mnot.net added the comment: I'm using it from HTMLParser; try to parse a document with the DTD given when error is something like: def error(self, msg): self.errors += 1 and it will loop. -- ___ Python tracker rep

[issue8885] markerbase declaration errors aren't recoverable

Mark Nottingham m...@mnot.net added the comment: Attaching test case. -- Added file: http://bugs.python.org/file17623/testcase_8885.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8885

[issue8885] markerbase declaration errors aren't recoverable

Mark Nottingham m...@mnot.net added the comment: http://svn.python.org/view/python/trunk/Lib/markupbase.py?view=log -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8885

[issue8885] markerbase declaration errors aren't recoverable

New submission from Mark Nottingham m...@mnot.net: In markupbase.py's ParserBase.parse_declaration, an unexpected character is caught like this: else: self.error( unexpected %r char in declaration % rawdata[j]) However, the position (j) isn't

[issue8885] markerbase declaration errors aren't recoverable

Mark Nottingham m...@mnot.net added the comment: Just to be clear -- if error() returns, it will cause an infinite loop. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8885