URI parsing barfs on '^'

ruby-talk
1

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

2

My guess is that Ruby's URI parser takes its inspiration from RFC 2396, which uri/common.rb refers to:

2.4.3. Excluded US-ASCII Characters

    unwise = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`"

    Data corresponding to excluded characters must be escaped in order to
    be properly represented within a URI.

http://www.ietf.org/rfc/rfc2396.txt

Cheers

···

On May 06, 2006, at 11:55, Alex Young wrote:

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?

--
PA, Onnay Equitursay
http://alt.textdrive.com/

3

PA wrote:

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?

My guess is that Ruby's URI parser takes its inspiration from RFC 2396, which uri/common.rb refers to:

2.4.3. Excluded US-ASCII Characters

   unwise = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`"

   Data corresponding to excluded characters must be escaped in order to
   be properly represented within a URI.

http://www.ietf.org/rfc/rfc2396.txt

Gotcha. Thought it'd be something obvious...

···

On May 06, 2006, at 11:55, Alex Young wrote:

--
Alex