[PATCH] percent-encoding for libfetch

[Ed Maste]

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