From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: PATH_INFO spec (with regard to ";")
Date: Sun, 13 Dec 2009 13:41:11 +0000 [thread overview]
Message-ID: <66B2EAE4-0FB8-431E-939B-98FBC4FF30C5@gmail.com> (raw)
In-Reply-To: <200912110119.49974.ibc@aliax.net>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On 11 Dec 2009, at 00:19, Iñaki Baz Castillo wrote:
> El Viernes, 11 de Diciembre de 2009, James Tucker escribió:
>>> Of course, in the grand scheme of things, hardly anybody uses ";" in
>>> paths. Yay for rare corner cases making our lives difficult.
>>
>> Amen, because I feel like I want to say "be configurable", given all of the
>> above.
>
> 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.
"Wrong" is hard to define with archaic protocol specifications that do not match "common" usage patterns, which is why I suggested it should be configurable. I would probably suggest to you that you make your client configurable to escape it's semi-colon characters in the uri that are not part of query syntax.
>
> Regards.
>
>
>
> --
> Iñaki Baz Castillo <ibc@aliax.net>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3679 bytes --]
next prev parent reply other threads:[~2009-12-13 13:41 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 [this message]
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
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=66B2EAE4-0FB8-431E-939B-98FBC4FF30C5@gmail.com \
--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).