Hello again :)
I apologise, but i've misunderstood Twitter 'needs' for verifying credentials. They want GET to be sent with Request Header, not POST (however new POST ContentType will be really useful).
Here's what Twitter needs:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials
Following Wikipedia:
http://en.wikipedia.org/wiki/Basic_access_authentication - Client request (user name "Aladdin", password "open sesame") part,
I need to send
Header: Authorization: Basic ${Base64Encoded(User:Password)}
ContentType: application/x-www-form-urlencoded
as GET request.
Could you provide similiar triggers to Read Resource as in HTTP POST?
Regards!
Jakub Tutaj
Neoprimus.com
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign