Just a heads-up to anyone else working with the twitter API today... I was in the middle of debugging an app when all of a sudden my authorize functions stopped working and I could no longer get access tokens from the twitter API. Because they had been working just fine, I thought it was something I had done even though what I was doing had nothing to do with that. It took me a while to track it down. Turns out, just today twitter started enforcing the use of SSL with their API calls. If you have any twitter API code that do not currently use "HTTPS" in it's endpoint URL's, better get that updated right away.
Twitter has been posting about it here: https://dev.twitter.com/discussions/24239 ... but it wasn't until my non-https API calls stopped working that I found out about it. Hope this post saves some folks some time. Kind regards, Jordan Michaels ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357425 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
