From: Alex Young <alex@...>
Date: 2006-05-06T18:55:44+09:00
Subject: URI parsing barfs on '^'

Hi there,

I've got a URL that appears valid, but that URI.parse breaks on.  I'm 
not sure what's correct here.  This URI parses, but is wrong:

  http://uk.finance.yahoo.com/q/cp?s=FTSE

This URI doesn't parse, and is correct:

  http://uk.finance.yahoo.com/q/cp?s=^FTSE

The question is, should '^' need to be quoted?  It's not named as a 
reserved character in RFC 3986, which I *think* is the most recent URI 
definition, so shouldn't URI.parse be able to handle it?

-- 
Alex