Which RFC is currently considered for urllib.pars?
Hello there, Would that be possible to make it clear which RFC is followed by the urllib.parse? The documentation states rfc 1808, which 10+ years old. However at the bottom of the doc the newest RFC 3986 is also mentioned, but it's not necessarily clear it's just for reference. Thanks Andrea Moro
Hi Andrea,
Would that be possible to make it clear which RFC is followed by the urllib.parse?
According to the urllib.parse docstring: urlparse module is based upon the following RFC specifications. RFC 3986 (STD66): "Uniform Resource Identifiers" by T. Berners-Lee, R. Fielding and L. Masinter, January 2005. RFC 2732 : "Format for Literal IPv6 Addresses in URL's by R.Hinden, B.Carpenter and L.Masinter, December 1999. RFC 2396: "Uniform Resource Identifiers (URI)": Generic Syntax by T. Berners-Lee, R. Fielding, and L. Masinter, August 1998. RFC 2368: "The mailto URL scheme", by P.Hoffman , L Masinter, J. Zawinski, July 1998. RFC 1808: "Relative Uniform Resource Locators", by R. Fielding, UC Irvine, June 1995. RFC 1738: "Uniform Resource Locators (URL)" by T. Berners-Lee, L. Masinter, M. McCahill, December 1994 RFC 3986 is considered the current standard and any future changes to urlparse module should conform with it. The urlparse module is currently not entirely compliant with this RFC due to defacto scenarios for parsing, and for backward compatibility purposes, some parsing quirks from older RFCs are retained. The testcases in test_urlparse.py provides a good indicator of parsing behavior. Do you think we should add this information to the HTML doc? -- Julien Palard https://mdk.fr
participants (2)
-
Andrea Moro -
Julien Palard