Norbert said
<<<
You have a colon in the name of the header. I?m not sure zinc removes it.
It could be a problem.
>>>
Ah, spot on. Apparently, we need the colon for Curl, but not for Pharo.
Also, response setAuthorization turned out to be the best approach. For
anyone searching this list, in the
Duh. Yes, there should be not colon at the end of the header name.
> On 27 Aug 2018, at 21:12, Norbert Hartl wrote:
>
> You have a colon in the name of the header. I‘m not sure zinc removes it. It
> could be a problem.
>
> Norbert
>
> Am 27.08.2018 um 20:23 schrieb Andy Burnett :
>
>> I am b
You have a colon in the name of the header. I‘m not sure zinc removes it. It
could be a problem.
Norbert
> Am 27.08.2018 um 20:23 schrieb Andy Burnett :
>
> I am building some pharo scripts to edit tasks in the Asana.com system.
>
> I have generated a Personal Access Token, and the terminal co
Have a look at
ZnClient>>#username:password:
ZnClient>>#setBasicAuthenticationUsername:password:
ZnRequest>>#setBasicAuthenticationUsername:password:
ZnRequest>>#setAuthorization:
and their senders. This should get you started. It is possible/probable that
you have to set the #url: before you m
On Tue, 28 Aug 2018 at 02:25, Andy Burnett
wrote:
> I am building some pharo scripts to edit tasks in the Asana.com system.
>
> I have generated a Personal Access Token, and the terminal command of:
>
> curl -H "Authorization: Bearer 12345abc"
> https://app.asana.com/api/1.0/users/me
>
> Returns
