Re: [WebDNA] HTTP post help
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108139
interpreted = N
texte = This is a multi-part message in MIME format. --------------060708080408060603080001 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Last I checked, you can't access the Facebook API with pure WebDNA. Examples of work arounds: 1. JavaScript: http://www.kanuhawaii.org/story/?id=132443179021346 Click on the FB Wall icon on the right hand side. This is written in pure JS using the FB JS API. I do take in variables from the JS API so I can store saves via WebDNA. 2. PHP/WebDNA http://www.kanuhawaii.org/login/ The login button goes to FB then returns to a PHP page on our server which uses the standard PHP API. I added a few lines of code so PHP could work with WebDNA. PHP passes a WebDNA page variables, gets a response, and I deal with the response in PHP. Hope this helps. aaronmichaelmusic@gmail.com wrote: > 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. > > I 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. From 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, >> >> Your code produces the following [callresponse] (facebook's webpage html?): >> ___________________________________________________________________________ >>
Redirecting...> http-equiv="refresh" >> content="0;url=http://www.facebook.com/common/browser.php" >> /> >> ___________________________________________________________________________ >> >> This is returned when I add www to connectHOST. call response is blank >> without www >> >> Dave >> ___________________________________________________________________________ >> >> >> 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 >>>