[Pharo-users] ZnClient and percent characters

Hello, I am attempting to use ZnClient to request data. The request requires a %2C (comma) delimited string as part of the query. Below is a snippet. znClient addPath: '/v1/instruments'; queryAt: 'fields' putAll: 'displayName%2Cinstrument%2Cpip'; get ; contents)

Re: [Pharo-users] ZnClient and percent characters

El Wed, 10 Jun 2015 10:14:37 -0500 Jimmie Houchin escribió: > Hello, > > I am attempting to use ZnClient to request data. The request requires > a %2C (comma) delimited string as part of the query. Below is a > snippet. > > znClient > addPath: '/v1/instruments'; > queryAt: 'fie

Re: [Pharo-users] ZnClient and percent characters

> On 10 Jun 2015, at 17:24, David wrote: > > El Wed, 10 Jun 2015 10:14:37 -0500 > Jimmie Houchin > escribió: >> Hello, >> >> I am attempting to use ZnClient to request data. The request requires >> a %2C (comma) delimited string as part of the query. Below is a >> snippet. >> >> znClient >>

Re: [Pharo-users] ZnClient and percent characters

On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: On 10 Jun 2015, at 17:24, David wrote: El Wed, 10 Jun 2015 10:14:37 -0500 Jimmie Houchin escribió: Hello, I am attempting to use ZnClient to request data. The request requires a %2C (comma) delimited string as part of the query. Below is

Re: [Pharo-users] ZnClient and percent characters

On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: On 10 Jun 2015, at 17:24, David wrote: El Wed, 10 Jun 2015 10:14:37 -0500 Jimmie Houchin escribió: Hello, I am attempting to use ZnClient to request data. The request requires a %2C (comma) delimited string as part of the query. Below is a

Re: [Pharo-users] ZnClient and percent characters

That's because the comma does not need to be escaped in the query part of the uri. Norbert > Am 10.06.2015 um 22:00 schrieb Jimmie Houchin : > > On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: >>> On 10 Jun 2015, at 17:24, David wrote: >>> >>> El Wed, 10 Jun 2015 10:14:37 -0500 >>> Jimmi

Re: [Pharo-users] ZnClient and percent characters

I am not an expert on URIs or encoding. However, this is a requirement of the API I am using and I am required to submit an encoded URI with %2C and no commas. As far as commas needing to be escaped, it seems from other sources that they should be. From https://www.ietf.org/rfc/rfc2396.txt

Re: [Pharo-users] ZnClient and percent characters

Just to clarify: "Characters in the "reserved" set are not reserved in all contexts. The set of characters actually reserved within any given URI component is defined by that component. In general, a character is reserved if the semantics of the URI changes if the character is replaced

Re: [Pharo-users] ZnClient and percent characters

this out. Meanwhile, this will enable you to get moving. Hope this helps Peter Kenny From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Norbert Hartl Sent: 10 June 2015 23:56 To: Pharo users users Subject: Re: [Pharo-users] ZnClient and percent characters

Re: [Pharo-users] ZnClient and percent characters

rt Hartl *Sent:* 10 June 2015 23:56 *To:* Pharo users users *Subject:* Re: [Pharo-users] ZnClient and percent characters Just to clarify: "Characters in the "reserved" set are not reserved in all contexts. The set of characters actually reserved within any given URI componen

Re: [Pharo-users] ZnClient and percent characters

Thanks for the reply. I implemented Peter's suggestion as an easy keep moving solution. As I said, I am not expert in what is or is not legal according to the standards. However, looking at Python, their urllib library in the quote and urlencode methods they encode the commas by default. _AL

Re: [Pharo-users] ZnClient and percent characters

@everybody The key method that defines how the query part of a URL is percent encoded is ZnMetaResourceUtils class>>#querySafeSet Years ago, Zinc HTTP Components followed the better safe than sorry approach of encoding almost every character except for the ones that are safe in all contexts.

Re: [Pharo-users] ZnClient and percent characters

ving. > > Hope this helps > > Peter Kenny > > From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of > Norbert Hartl > Sent: 10 June 2015 23:56 > To: Pharo users users > Subject: Re: [Pharo-users] ZnClient and percent characters > > J

Re: [Pharo-users] ZnClient and percent characters

users users Subject: Re: [Pharo-users] ZnClient and percent characters Just to clarify: "Characters in the "reserved" set are not reserved in all contexts. The set of characters actually reserved within any given URI component is defined by that component. In general, a cha

Re: [Pharo-users] ZnClient and percent characters

> On 11 Jun 2015, at 9:51 , PBKResearch wrote: > > I don’t quite understand Norbert’s comment. Does ‘monkey’ apply to me or to > what I have done? Either way, it seems unnecessary and abusive. It's a phrase to describe the change: http://en.wikipedia.org/wiki/Monkey_patch

Re: [Pharo-users] ZnClient and percent characters

ubject: Re: [Pharo-users] ZnClient and percent characters @everybody The key method that defines how the query part of a URL is percent encoded is ZnMetaResourceUtils class>>#querySafeSet Years ago, Zinc HTTP Components followed the better safe than sorry approach of encoding almost every char

Re: [Pharo-users] ZnClient and percent characters

-users [mailto:pharo-users-boun...@lists.pharo.org >> <mailto:pharo-users-boun...@lists.pharo.org>] On Behalf Of Norbert Hartl >> Sent: 10 June 2015 23:56 >> To: Pharo users users >> Subject: Re: [Pharo-users] ZnClient and percent characters >> >> Just to cl

Re: [Pharo-users] ZnClient and percent characters

This is exactly why I expressly state I am not a language lawyer and explicitly do not know what is and is not expressly forbidden or allowed with regards to a comma. You are correct about the Wikipedia article. Is it every wrong or illegal to use a complete safely encoded request? Is it just

Re: [Pharo-users] ZnClient and percent characters

> On 11 Jun 2015, at 08:35, Sven Van Caekenberghe wrote: > > @everybody > > The key method that defines how the query part of a URL is percent encoded is > ZnMetaResourceUtils class>>#querySafeSet > > Years ago, Zinc HTTP Components followed the better safe than sorry approach > of encoding

Re: [Pharo-users] ZnClient and percent characters

Here is one older discussion that let to Zn going away from the better safe than sorry approach to encoding: http://forum.world.st/Zinc-How-to-use-the-character-in-an-URL-td4716386.html#a4716459 You have to read it up to the end. > On 11 Jun 2015, at 16:19, Jimmie Houchin wrote: > > This is e

Re: [Pharo-users] ZnClient and percent characters

for encoding of commas as the safe default, which can be overridden if necessary. Peter Kenny From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Norbert Hartl Sent: 11 June 2015 11:25 To: Pharo users users Subject: Re: [Pharo-users] ZnClient and percent characters

Re: [Pharo-users] ZnClient and percent characters

boun...@lists.pharo.org] On Behalf Of > Norbert Hartl > Sent: 11 June 2015 11:25 > To: Pharo users users > Subject: Re: [Pharo-users] ZnClient and percent characters > > No offense meant. I assumed you would know the term. Sorry! Henry explained > it quite good what

Re: [Pharo-users] ZnClient and percent characters

On 06/11/2015 09:48 AM, Sven Van Caekenberghe wrote: Here is one older discussion that let to Zn going away from the better safe than sorry approach to encoding: http://forum.world.st/Zinc-How-to-use-the-character-in-an-URL-td4716386.html#a4716459 You have to read it up to the end. On 11 J

Re: [Pharo-users] ZnClient and percent characters

yway that's my 2p worth. Peter Kenny -Original Message- From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Sven Van Caekenberghe Sent: 11 June 2015 15:49 To: Any question about pharo is welcome Subject: Re: [Pharo-users] ZnClient and percent characters Here i

Re: [Pharo-users] ZnClient and percent characters

Hi, first off, I found this article a good read on the topic: http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-about-url-encoding > One thing which has not been looked at in this di

Re: [Pharo-users] ZnClient and percent characters

Hi all, Sven, I think what many people need is to have a ZnClient subclass that follows the ‘better safe than sorry’ approach. In this way, there is an easy escape when someone bumps into a server that is not strictly implementing the standard. We bumped into this too with the + character when

Re: [Pharo-users] ZnClient and percent characters

...@lists.pharo.org] On Behalf Of Norbert Hartl Sent: 11 June 2015 17:07 To: Pharo users users Subject: Re: [Pharo-users] ZnClient and percent characters Am 11.06.2015 um 16:51 schrieb PBKResearch mailto:pe...@pbkresearch.co.uk> >: Norbert Apology accepted – I had never heard this

Re: [Pharo-users] ZnClient and percent characters

> that does not make my views any less valid. dito. Let's close this case. To me it is a little misunderstanding that took the wrong route. Norbert > > Peter Kenny > > > From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of > Norbert

Re: [Pharo-users] ZnClient and percent characters

Peter Kenny From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Norbert Hartl Sent: 11 June 2015 17:07 To: Pharo users users Subject: Re: [Pharo-users] ZnClient and percent characters Am 11.06.2015 um 16:51 schrieb PBKResearch < <mailto:pe...@pbkr