[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 mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 didn't emit a Host header, and the excuse were But we only advertise ourselves as HTTP/1.0. The biggest difference being that this has additional security impact. The pain of lack of support for SNI is completely borne by the server-side, not the client (here, Python). As such, this is not a feature for Python client-side developers, but an interop / scaling / security issue for the Web and Internet overall. -- nosy: +mnot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5639 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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://git.openssl.org/gitweb/?p=openssl.git;a=blob;f=NEWS -- components: Extension Modules messages: 207660 nosy: mnot priority: normal severity: normal status: open title: ALPN support for TLS type: enhancement versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20188 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 information. import socket sock = socket.socket() sock.connect( (python.org, 80) ) sock.send(bGET / HTTP/1.0\r\n\r\n) 18 buf = bytearray(b * 10) sock.recv_into(buf) 10 print buf HTTP/1.1 3 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7827 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 tracker rep...@bugs.python.org http://bugs.python.org/issue7097 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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...@bugs.python.org http://bugs.python.org/issue8885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 updated, which means that error() will be called again once it returns. For example, this declaration: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd (which I think is generated by MS Office) will trigger this behaviour. Two possible resolutions: 1) increment J and try the next character in this case 2) document that error() is not recoverable; i.e., it MUST raise an exception. My preference is strongly for #1 (as HTML parsing should be forgiving, and HTMLParser is based upon markerbase). -- components: Library (Lib) messages: 106938 nosy: mnot priority: normal severity: normal status: open title: markerbase declaration errors aren't recoverable type: behavior versions: Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
