Great help Taylor thanks...
Will check on that and come back to you.

thanks again

On Tue, May 11, 2010 at 13:20, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Sebastian,
>
> Also make sure that all of the following points are true in your
> implementation:
>
>   * You are using POST
>   * You are using SSL
>   * Your xAuth parameters are the ONLY parameters in your POST body
>   * You're setting a Content-Type header of
> "application/x-www-form-urlencoded"
>   * Your xAuth parameters are properly part of your signature base string,
> where they will appear at the end of the signature base string in
> alphabetical order
>   * You're using HTTP header-based OAuth -- not attaching OAuth parameters
> to the URL or POST body
>   * You're HTTP Authorization header should only have oauth_* parameters in
> it, not any of the xauth parameters
>
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>
>
>
> On Tue, May 11, 2010 at 9:07 AM, sebastian gomez <
> sebastiangomezcor...@gmail.com> wrote:
>
>> will do that, thanks
>>
>>
>> On Tue, May 11, 2010 at 12:53, Cameron Kaiser <spec...@floodgap.com>wrote:
>>
>>> > Ok, when I uset POST I get a 401 (Unauthorized) :(
>>> > I guess I'm doing something wrong... what could it be? is my base
>>> string ok?
>>>
>>> The server should give you a message like "Invalid nonce" or "Invalid
>>> signature" or some such. If you don't even get that, I suspect your xAuth
>>> access is not working or set up. Mail a...@twitter.com.
>>>
>>> --
>>> ------------------------------------ personal:
>>> http://www.cameronkaiser.com/ --
>>>  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
>>> ckai...@floodgap.com
>>> -- BOND THEME NOW PLAYING: "Diamonds Are Forever"
>>> -----------------------------
>>>
>>
>>
>

Reply via email to