Re: [WebDNA] TCPConnect w/ user:pass
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102536
interpreted = N
texte = UTF made no diff... and now that I think about it it shouldn't, since the= UTF declaration happens=20client-side *after* the [TCPConnect] fires server-side. [shell]curl[/shel=l] seems like the way to=20go here for me...-DanOn Mon, 11 May 2009 17:47:53 +0100 Tom Duke
wrote:> Dan,> Hmmmm... you tell the truth. I obviously didn't read the api docs clo=sely> ;-) I have however now tested it against an api call that requires> authentication, and it does seem to work (code below).>=20> Just one thought - I'm pretty sure twitter expects UTF-8 encoding. Is =it> possible that your template that makes the call is using a different> character set and maybe the username or password contains a character t=hat> is being encoded incorrectly?>=20> - Tom>=20>=20>=20>=20>=20> [!]>=20> ------------------------------------> ### Connect to twitter and pull down user's followers ###>=20> [/!][TCPConnect host=3Dtwitter.com][!]> [/!][text]xmlresponse=3D[tcpsend skipheader=3DT]GET /statuses/followers=.xml> HTTP/1.0[unurl]%0D%0A[/unurl][!]> [/!]Authorization: Basic [encrypt> method=3DBase64][user_id]:[user_pw][/encrypt][unurl]%0D%0A[/unurl][!]> [/!][unurl]%0D%0A%0D%0A[/unurl][/tcpsend][/text][!]> [/!][/tcpconnect][!]>=20> [/!][xmlresponse]
Associated Messages, from the most recent to the oldest:
UTF made no diff... and now that I think about it it shouldn't, since the= UTF declaration happens=20client-side *after* the [tcpconnect] fires server-side. [shell]curl[/shel=l] seems like the way to=20go here for me...-DanOn Mon, 11 May 2009 17:47:53 +0100 Tom Duke wrote:> Dan,> Hmmmm... you tell the truth. I obviously didn't read the api docs clo=sely> ;-) I have however now tested it against an api call that requires> authentication, and it does seem to work (code below).>=20> Just one thought - I'm pretty sure twitter expects UTF-8 encoding. Is =it> possible that your template that makes the call is using a different> character set and maybe the username or password contains a character t=hat> is being encoded incorrectly?>=20> - Tom>=20>=20>=20>=20>=20> [!]>=20> ------------------------------------> ### Connect to twitter and pull down user's followers ###>=20> [/!][TCPConnect host=3Dtwitter.com][!]> [/!][text]xmlresponse=3D[tcpsend skipheader=3DT]GET /statuses/followers=.xml> HTTP/1.0[unurl]%0D%0A[/unurl][!]> [/!]Authorization: Basic [encrypt> method=3DBase64][user_id]:[user_pw][/encrypt][unurl]%0D%0A[/unurl][!]> [/!][unurl]%0D%0A%0D%0A[/unurl][/tcpsend][/text][!]> [/!][/tcpconnect][!]>=20> [/!][xmlresponse]
"Dan Strong"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] Gulf Coast WebDNA programmers (2010)
View order not right (1997)
Apoligy (1997)
Shopping carts and reloading pages (1997)
Pirated WebCat? NOT... (2003)
A quick look (2003)
WebCatalog can't find database (1997)
[WebDNA] linux fix for date to day of week (2008)
Am I going senile? (Price recalc based on quantity) (1997)
Problem with Formulas.db (1998)
FAX orders (1996)
[OT] (waaaay OT) (2004)
Format question WC Mac f3 (1997)
Further tests with the infamous shipCost (1997)
Director 7 (1999)
GuestBook example (1997)
Referring URL (1998)
[shownext] (1998)
RE: protect tag not working (1998)
Trouble with formula.db (1997)