We'll be correcting this on Monday instead of today, folks.

Have a great weekend.

Taylor

On Friday, March 12, 2010, Taylor Singletary
<taylorsinglet...@twitter.com> wrote:
> Hello Developers,
>
> Though it certainly would be more correct for us to properly set the
> Content-Type HTTP header throughout the OAuth token acquisition
> process to "application/x-www-form-urlencoded," it has caused some
> issues with a number of applications. This afternoon we will restore
> the original behavior of setting the Content-Type header to "text/
> html".
>
> Being in compliance with the OAuth specification is important to us.
> Consider our old behavior now on deprecation notice. In four weeks or
> so we'll begin setting the Content-Type header correctly again. We'll
> announce a more formal deprecation date within a week of deployment.
>
> We invite you to do the right thing with us.
>
> Thanks!
>
> Taylor
> http://twitter.com/episod
>

-- 
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod

Reply via email to