RE: [xri] Encoding plus (+) sign

["Wachob, Gabe" <gwachob@visa.com>]

I don't think they have to be encoded.

 

The query part of a URI has relatively few requirements for escaping/encoding relative to the rest of the URI.

 

We should consult the RFC 3986 spec to answer this question - we should require no more encoding/escaping than is required by that spec.

 

   -Gabe

---

From: Tan, William [mailto:William.Tan@neustar.biz]
Sent: Wednesday, May 10, 2006 11:13 AM
To: Drummond Reed; xri@lists.oasis-open.org
Subject: RE: [xri] Encoding plus (+) sign

What about non-ASCII characters in the resolution parameter? They would have to be % encoded in IRI style anyway, right? I doubt these parameters would be intelligible to the layperson by any standard anyway, why not just specify that they be URL encoded (rfc1738), which includes encoding % to %25?

 

=wil (http://xri.net/=wil)

 

 

---

From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Wednesday, May 10, 2006 3:04 PM
To: Tan, William; xri@lists.oasis-open.org
Subject: RE: [xri] Encoding plus (+) sign

 

So, Wil, are you thinking that we should only specify percent-encoding of the plus sign? While that’s simple, it seems a little bit of an odd rule. Since this only applies to XRI proxy servers, wouldn’t it be easier for proxy server implementers to just make sure their code leaves the plus sign alone?

 

That way we wouldn’t need any special encoding of the resolution parameters at all.

 

Thoughts?

 

=Drummond

 

---

From: Tan, William [mailto:William.Tan@neustar.biz]
Sent: Monday, May 08, 2006 6:50 PM
To: Drummond Reed; xri@lists.oasis-open.org
Subject: RE: [xri] Encoding plus (+) sign

 

No, slashes are fine.

I don’t know of any other strange character other than the plus sign.

 

=wil (http://xri.net/=wil)

 

 

---

From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Tuesday, May 09, 2006 11:20 AM
To: Tan, William; xri@lists.oasis-open.org
Subject: RE: [xri] Encoding plus (+) sign

 

I was offline at the Internet Identity Workshop last week so I just got to this.

 

This seems like it is hugely important from an interoperability standpoint. Either we need to require all proxy HXRI parameters to use percent-encoding for all XRI reserved characters (which is a big deal) or we need some other solution.

 

How do others feel?

 

Wil, would this also extend to forward slash characters?

 

=Drummond

 

---

From: Tan, William [mailto:William.Tan@neustar.biz]
Sent: Monday, May 01, 2006 3:25 AM
To: xri@lists.oasis-open.org
Subject: [xri] Encoding plus (+) sign

 

Hi XRItes,

 

The resolution specification does not say that we have to URL-escape the query parameters before merging it into the proxy URI. However, our most important MIME type “application/xrds+xml” contains a plus sign which has special legacy meaning which gets decoded as a space character on the server side. The parameter values could get corrupted if we don’t escape it, especially when merging with existing QXRI query string. So, my argument is to require that the query parameter values be URL-encoded (by that I mean percent encoding any symbol in the “iquery” production).

 

=wil (http://xri.net/=wil)