Changing the Content-Type header for OAuth token exchanges

[Mark McBride]

All - 

Per issue 1263 (http://code.google.com/p/twitter-api/issues/detail?id=1263) (and the OAuth spec), we're looking to change the Content-Type header for OAuth token exchanges to 'application/x-www-form-urlencoded'.  To date it has been 'text/html'.  We want to ensure that this will not break existing applications, so if you have any qualms please voice them here.

  ---Mark

http://twitter.com/mccv

[Marcel Molina]

This change has been deployed. Let us know if things get wonky.

--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio

[Kevin Wallace]

This change has broken Twitter support in our iPhone apps (Runmeter,
Walkmeter, and Cyclemeter). (They're among the top 100 iPhone apps in
the App Store's Health and Fitness category.) Our customers are
starting to write us because they cannot connect to Twitter using our
app which uses Sign In With Twitter and OAuth. We would greatly
appreciate it if you would go back to text/plain, at least until we
can release versions of our app that will accept application/x-www-
form-urlencoded. Otherwise our customers are screwed until then.

Kevin Wallace
Abvio LLC
Founder

On Mar 10, 1:13 pm, Marcel Molina <mar...@twitter.com> wrote:
> This change has been deployed. Let us know if things get wonky.
>