From owner-freebsd-current@FreeBSD.ORG  Mon Apr  9 23:26:40 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1426F1065670;
	Mon,  9 Apr 2012 23:26:39 +0000 (UTC)
	(envelope-from emaste@freebsd.org)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134])
	by mx1.freebsd.org (Postfix) with ESMTP id C833F8FC17;
	Mon,  9 Apr 2012 23:26:38 +0000 (UTC)
Received: from labgw2.phaedrus.sandvine.com (192.168.222.22) by
	WTL-EXCH-1.sandvine.com (192.168.196.31) with Microsoft SMTP Server id
	14.1.339.1; Mon, 9 Apr 2012 19:26:38 -0400
Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 10332)	id
	E807E33C02; Mon,  9 Apr 2012 19:26:35 -0400 (EDT)
Date: Mon, 9 Apr 2012 19:26:35 -0400
From: Ed Maste <emaste@freebsd.org>
To: Julian Elischer <julian@freebsd.org>
Message-ID: <20120409232635.GA51176@sandvine.com>
References: <20120409205051.GA27392@sandvine.com>
	<4F83619E.5060607@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4F83619E.5060607@freebsd.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-current@freebsd.org
Subject: Re: [PATCH] percent-encoding for libfetch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Apr 2012 23:26:40 -0000

On Mon, Apr 09, 2012 at 03:24:30PM -0700, Julian Elischer wrote:

> could you not parse the @ differently depending upon where it is?
> 
> others must have covered this problem..

Indeed others have - none other than T. Berners-Lee, in RFC 1738 where
the format of a URL is specified:

  In addition, octets may be encoded by a character triplet consisting
  of the character "%" followed by the two hexadecimal digits (from
  "0123456789ABCDEF") which forming the hexadecimal value of the octet.
  (The characters "abcdef" may also be used in hexadecimal encodings.)

  ...

  The user name (and password), if present, are followed by a
  commercial at-sign "@". Within the user and password field, any ":",
  "@", or "/" must be encoded.

-Ed