Re: [Chicken-users] Ann: url egg 3.0

[Kon Lovett]

On Jun 5, 2007, at 6:23 AM, John Cowan wrote:

> Kon Lovett scripsit:
>
> > I think a bug. Doesn't matter what the RFC says, it should have
> > something well defined as a value. Currently the query component must
> > be composed of <key>\s=\s<value>, but <key> should be ok. The <value>
> > should be defaulted - optional argument or parameter otherwise?
>
> RFC 3986 in fact allows any sequence of pchars (plus "/" and "?")  
> in the
> query string.  If you want to decode it into a sequence of name=value
> pairs separated by & or ;, that's great, but it's a higher-level  
> protocol
> used by HTTP forms, not part of URI syntax.

Decode Query is higher level syntax. But maybe not high level enough  
now that scheme specific has been added, I must check.

Parsing the query component is part of the default URI scheme handler.

"/" and "?" are legal. It scans from the left.

> Also, if by "\s" you mean space, spaces are not allowed in URIs.

Well, %20 is okay-doky. It was late & I wanted to set-off the '='  
character. By the time it is parsing a query '%' decoding has been done.

> --
> John Cowan   address@hidden    http://ccil.org/~cowan
> The known is finite, the unknown infinite; intellectually we stand
> on an islet in the midst of an illimitable ocean of inexplicability.
> Our business in every generation is to reclaim a little more land,
> to add something to the extent and the solidity of our possessions.
>         --Thomas Henry Huxley