[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] ED07 Issue #1: Encoding of + in query parameters
Victor, Will specifying that a literal space must be encoded as %20 if its included solve the problem? =ve7jtb On 24-Oct-07, at 9:56 AM, Victor Grey wrote: >> So the only thing we have to do to make the whole thing just work, >> is forbid spaces in QXRI query params -- whether they are escaped >> or not. > > On reflection, I thought I should clarify this a bit: > > Since the "+" symbol is a legacy encoding of the space character in > URL query params, all of (at least) the LAMP languages unescape "+" > to a space. > > Since we -need- the "+" character in QXRI query params for mime- > types, we deal with this in our php and ruby implementations by > simply converting spaces in the query params back to "+"s. > > This means that any actual space in a query param is going to get > un-unescaped to a "+", whether it was originally percent encoded or > not. > > There are two ways to deal with this: > 1. Require the "+" character in QXRI query params to be percent > encoded. > 2. State that QXRI query params SHOULD NOT contain spaces, escaped > or otherwise, as they may be misinterpreted by applications as a > "+" character. > > I prefer 2. > > I've never actually seen a literal space used in a query param, I > think it would be quite rare. Further uglifying QXRI query params > by requiring the "+" to be percent encoded to cover this rare > corner case doesn't seem worth it to me. > > =vg > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs > in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]