On Tue, Jan 15, 2013 at 3:03 PM, Ivan Raikov ivan.g.rai...@gmail.comwrote:
Percent-encoded sequences of more than one octet will not get touched by
pct-decode in the current implementation, so you will not get double
escaping. Percent-encoded sequences of one octet will get decoded if they
On Tue, Jan 15, 2013 at 06:07:06PM +0900, Alex Shinn wrote:
On Tue, Jan 15, 2013 at 3:03 PM, Ivan Raikov ivan.g.rai...@gmail.comwrote:
Percent-encoded sequences of more than one octet will not get touched by
pct-decode in the current implementation, so you will not get double
escaping.
On Tue, Jan 15, 2013 at 07:30:07PM +0900, Alex Shinn wrote:
Right, I'm familiar with the evil standards :) I'm also hoping that we can
have some basic compatibility between Chicken's uri module and Chibi's
(and whatever R7RS WG2 comes up with).
That would be nice indeed.
It seems to me the
On Tue, Jan 15, 2013 at 7:48 PM, Peter Bex peter@xs4all.nl wrote:
These special characters are called reserved in the BNF. As you can
see, the question mark, equals sign and ampersand is in there.
For query urlencoded query strings, these *cannot* be decoded, because
then you can't
On Wed, Jan 16, 2013 at 12:39:16AM +0900, Alex Shinn wrote:
The internal representation is either decoded, or it is encoded.
Either can be made to work.
In this case, the decoded uri-common representation of the former is:
((bool-expr . xy=1))
and the decoded representation of the
I am developing a project which I expect will involve a number of extension
libraries, or plugins (a large number, many of them provided by third
parties, if my project ever becomes popular). For several reasons (which I
will explain on request if anyone is curious), I feel it is best *not* to
On Wed, Jan 16, 2013 at 12:59 AM, Peter Bex peter@xs4all.nl wrote:
On Wed, Jan 16, 2013 at 12:39:16AM +0900, Alex Shinn wrote:
The internal representation is either decoded, or it is encoded.
Either can be made to work.
In this case, the decoded uri-common representation of the
