Peter Bex <xxxxxx@more-magic.net> writes:

| The situation is somewhat confusing and weird, but it turns out
to be a good compromise, because whenever you need the
not-fully-decoded path, you can access the underlying uri-generic
object.  As long as you haven't manipulated any component, you
will get back the original input.

I've done the same thing in my URI parser.

I'm sure that your parser is better and more complete, by the way.
I designed mine only to handle URIs that I could imagine my own
server serving, leaving everything else out.  That makes having
this "escape valve" important in case I ever use it in a client or
a proxy or in some other situation where I can't control the form
of the URLs.