From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: url-expand.el and url-parse.el not conforming to RFC3986 Date: Sat, 28 Nov 2015 08:58:42 -0600 Message-ID: <8637vqw4pp.fsf@stephe-leake.org> References: <5a139835077940febe2fe3dfe624f754@rintintin.hq.realize.ch.lan.rit> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1448722763 27806 80.91.229.3 (28 Nov 2015 14:59:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Nov 2015 14:59:23 +0000 (UTC) Cc: "emacs-devel@gnu.org" To: "Alain Schneble \(Realize IT GmbH\)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 28 15:59:10 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a2gxx-0004Xq-AO for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2015 15:59:09 +0100 Original-Received: from localhost ([::1]:60999 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2gy0-0008Dz-7z for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2015 09:59:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49466) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2gxw-0008Ds-Hz for emacs-devel@gnu.org; Sat, 28 Nov 2015 09:59:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2gxr-0000MJ-Hw for emacs-devel@gnu.org; Sat, 28 Nov 2015 09:59:08 -0500 Original-Received: from gproxy7-pub.mail.unifiedlayer.com ([70.40.196.235]:46229) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1a2gxr-0000M4-Ap for emacs-devel@gnu.org; Sat, 28 Nov 2015 09:59:03 -0500 Original-Received: (qmail 9338 invoked by uid 0); 28 Nov 2015 14:58:57 -0000 Original-Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy7.mail.unifiedlayer.com with SMTP; 28 Nov 2015 14:58:57 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw4 with id n2yo1r00K2UdiVW012yreR; Sat, 28 Nov 2015 07:58:57 -0700 X-Authority-Analysis: v=2.1 cv=IekUBwaa c=1 sm=1 tr=0 a=CQdxDb2CKd3SRg4I0/XZPQ==:117 a=CQdxDb2CKd3SRg4I0/XZPQ==:17 a=DsvgjBjRAAAA:8 a=f5113yIGAAAA:8 a=9i_RQKNPAAAA:8 a=hEr_IkYJT6EA:10 a=x_XPkuGwIRMA:10 a=qtqOOiqGOCEA:10 a=e-BuMA0EOucNx3rtDasA:9 Original-Received: from [76.218.37.33] (port=62684 helo=TAKVER2) by host114.hostmonster.com with esmtpa (Exim 4.84) (envelope-from ) id 1a2gxc-0007xT-1V; Sat, 28 Nov 2015 07:58:48 -0700 In-Reply-To: <5a139835077940febe2fe3dfe624f754@rintintin.hq.realize.ch.lan.rit> (Alain Schneble's message of "Fri, 27 Nov 2015 15:22:29 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (windows-nt) X-Identified-User: {2442:host114.hostmonster.com:stephele:stephe-leake.org} {sentby:smtp auth 76.218.37.33 authed with stephen_leake@stephe-leake.org} X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 70.40.196.235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:195461 Archived-At: "Alain Schneble (Realize IT GmbH)" writes: > url-expand.el and url-parse.el seem to not follow RFC3986 "Uniform > Resource Identifier (URI): Generic Syntax" in some cases. But I guess > they should. So I started to study RFC3986 in more details and write > tests against url-expand-file-name and url-generic-parse-url (see > attached patch). > > The tests reveal the following issues: Thanks for writing these tests, and the fixes. > Please let me know if I should follow a different procedure to submit > these changes. I signed the copyright assignment "GNU EMACS" this > year. Please file a bug report (use M-x report-emacs-bug), and follow up here with the bug number. In the first bug report, just outline the issue. In a follow up bug report, attach the patch. -- -- Stephe