Re: [WebDNA] HTTP post help
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108138
interpreted = N
texte = Well, like I said, I haven't worked with the FB api yet, and I don't =know what your script is designed for. However, it appears that you are =connecting just fine but its not throwing anything back that clearly =indicates a malformed request. I typically expect to get back a string, =xml, jason, or some name-value pairs. Unfortunately, you may have to go =with Olin's suggestion. Last I looked at the FB api docs, they've been =pushing an all Javascript method. My hunch is that you don't need to be =POSTing this at all, but maybe opening a popup or something with =javascript. =20I did something similar to this with Google Calendar. It seems that I =generated a url that opened in a javascript popup. The user was =supposed to provide their authentication to access their calendar, then =it would redirect to a page that just contained a token. =46rom there, =I used JS to grab the token, close the popup, and then use that in my =TCP requests.Also, I'm not sure about OAUTH v1, but I know you can do all the proper =authentication with the OAUTH v2 in WebDNA.On Jan 19, 2012, at 5:40 PM, Dave Stengel wrote:> Aaron,>=20> Your code produces the following [callresponse] (facebook's webpage =html?):> =__________________________________________________________________________=_> =
Redirecting... http-equiv=3D"refresh"> content=3D"0;url=3Dhttp://www.facebook.com/common/browser.php"> />> =__________________________________________________________________________=_>=20> This is returned when I add www to connectHOST. call response is blank> without www>=20> Dave> =__________________________________________________________________________=_>=20>=20> On Thu, Jan 19, 2012 at 2:15 PM, wrote:>> BTW - I don't know if you're already doing this with your testing, =but put>> your TCP script inside of a text variable and reveal it inside of a>>