Re: PATH_INFO spec (with regard to ";")

["Iñaki Baz Castillo" <ibc@aliax.net>]

El Domingo, 13 de Diciembre de 2009, James Tucker escribió:
> 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.

Yes, modifications in the client could be an option. However I cannot force to 
every XCAP clients to escape ";" when it's allowed as per URI BNF grammar.


-- 
Iñaki Baz Castillo <ibc@aliax.net>