From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: rack-devel@googlegroups.com
Subject: Re: PATH_INFO spec (with regard to ";")
Date: Mon, 14 Dec 2009 21:50:31 +0100 [thread overview]
Message-ID: <200912142150.31421.ibc@aliax.net> (raw)
In-Reply-To: <20091214185158.GC12789@dcvr.yhbt.net>
El Lunes, 14 de Diciembre de 2009, Eric Wong escribió:
> Iñaki Baz Castillo <ibc@aliax.net> wrote:
> > I'm coding a XCAP server using Rack. XCAP is basically XPath over HTTP in
> > which there are HTTP URI's like the following:
> >
> > /auid/global/mydoc.xml/~~/ruleset/rule%5b@id=%22sip:dom.org;p=abc%22%5d
> >
> > After reading RFC for URI and HTTP I think that the ";" is valid into the
> > above URI. I also asked in a XCAP maillist and received same conclusion.
> >
> > Please tell me if you consider the ";" in the above URI wrong.
>
> Hi Iñaki,
>
> You're missing the point, it's not that ";" is right or wrong. It's
> "right" in that it's always been _accepted_ by the Mongrel family of
> HTTP parsers. That's not the issue.
>
> The issue is just whether or not the PATH_INFO variable can contain ";"
> (a path-segment parameter) in it. RFC 3875 section 4.1.5 states it
> cannot:
>
> Unlike a URI path, the PATH_INFO is not URL-encoded, and cannot
> contain path-segment parameters.
>
> However, Rack is not governed by RFC 3875 and already deviates from
> it when it comes to the "PATH_INFO is not URL-encoded".
Ok, thanks a lot for the clarification.
--
Iñaki Baz Castillo <ibc@aliax.net>
next prev parent reply other threads:[~2009-12-14 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 22:30 PATH_INFO spec (with regard to ";") Eric Wong
2009-12-11 0:03 ` James Tucker
2009-12-11 0:19 ` Iñaki Baz Castillo
2009-12-13 13:41 ` James Tucker
2009-12-13 15:15 ` Iñaki Baz Castillo
2009-12-14 0:44 ` Iñaki Baz Castillo
2009-12-14 11:08 ` James Tucker
2009-12-14 18:51 ` Eric Wong
2009-12-14 20:50 ` Iñaki Baz Castillo [this message]
2009-12-13 20:04 ` macournoyer
2009-12-13 20:49 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912142150.31421.ibc@aliax.net \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).