That link alone won't work as a GET (URL/address bar or clicking it).
You need to POST the consumer OAuth header and request values.

∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Fri, Sep 11, 2009 at 3:59 PM, Andrew Wojtowicz
<andrew.wojtow...@gmail.com> wrote:
> didnt work for me.
>
> Failed to validate oauth signature and token
>
> On Fri, Sep 11, 2009 at 3:44 PM, JDG <ghil...@gmail.com> wrote:
>>
>> I was just able to point to https://twitter.com/oauth/request_token (which
>> would obviously imply port 443) with no problem.
>>
>> On Fri, Sep 11, 2009 at 13:40, Andrew Badera <and...@badera.us> wrote:
>>>
>>> 9443 I think.
>>>
>>> ∞ Andy Badera
>>> ∞ +1 518-641-1280
>>> ∞ This email is: [ ] bloggable [x] ask first [ ] private
>>> ∞ Google me: http://www.google.com/search?q=andrew%20badera
>>>
>>>
>>>
>>> On Fri, Sep 11, 2009 at 11:51 AM, wojtowicza <andrew.wojtow...@gmail.com>
>>> wrote:
>>> >
>>> > What port does Twitter use for SSL?  we go through an ISA server and
>>> > by default it only allows port 443.  well twitter uses another port
>>> > for ssl.  i'm trying to find it so i can open it up for my users.
>>> >
>>> > thanks
>>> >
>>
>>
>>
>> --
>> Internets. Serious business.
>
>
>
> --
> Hunting the Wild's of New Jersey
> http://www.newjerseyhunter.com
>

Reply via email to