[twitter-dev] http://m.twitter.com/oauth/authorize is redirecting to https://mobile.twitter.com/
http://m.twitter.com/oauth/authorize is currently redirecting to https://mobile.twitter.com/. Earlier today I saw it redirecting to http://m.twitter.com/oauth or https://m.twitter.com/oauth (in the latter case via a certificate warning). http://twitter.com/oauth/authorize is behaving as expected. I assume this is some transient problem caused by some certificate/subdomain shakeup? If so, can anyone from Twitter provide an estimated time for a fix? (I just tried using mobile.twitter.com/oauth/authorize and ended up at https://mobile.twitter.com/oauth.) Thanks -- Richard -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Error messages during authorize and redirect processes (OAuth)
On Aug 27, 11:16 am, Matt Harris thematthar...@twitter.com wrote: To allow us to track the issue and to make sure it gets fixed can you file a bug report on our issues list: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/detail?id=1827 -- R -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] statuses/update: Expect: 100-Continue header rejected
I've been playing with oacurl https://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with we only allow the 100-continue expectation. This seems to violate http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20 Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token). Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Output from oacurl (duplicate content snipped) is below: /c/download: echo status=Testing+oacurl | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -v http://api.twitter.com/1/statuses/update.json POST /1/statuses/update.json HTTP/1.1 Content-Type: application/atom+xml Authorization: OAuth oauth_token=34507306-x, oauth_consumer_key=x, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274334015, oauth_nonce=508570714177400, oauth_version=1.0, oauth_signature=x Transfer-Encoding: chunked Host: api.twitter.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.0 (java 1.5) Expect: 100-Continue HTTP/1.1 417 Expectation Failed Date: Thu, 20 May 2010 05:38:21 GMT Server: hi Vary: Accept-Encoding Content-Length: 364 Connection: close Content-Type: text/html; charset=iso-8859-1 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title417 Expectation Failed/title /headbody h1Expectation Failed/h1 pThe expectation given in the Expect request-header field could not be met by this server./p pThe client sentpre Expect: 100-Continue /pre but we only allow the 100-continue expectation./p /body/html -- Richard
[twitter-dev] Re: statuses/update: Expect: 100-Continue header rejected
On May 20, 10:38 pm, Cameron Kaiser spec...@floodgap.com wrote: I've been playing with oacurlhttps://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with we only allow the 100-continue expectation. Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Just change the header to simply send a blank Expect:. With regular cURL a simple -H Expect: will work. Thanks for your reply. Although oacurl supports -H like curl, using -H Expect: adds a second Expect: header to the request, the Twitter server still fails because of Expect: 100-Continue. I'll raise the oacurl bug with one of the authors, but that still leaves a bug in Twitter's handling of Expect:. /c/download: echo status=Testing+oacurl | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -H Expect: -v http://api.twitter.com/1/statuses/update.json POST /1/statuses/update.json HTTP/1.1 Content-Type: application/atom+xml Expect: Authorization: OAuth oauth_token=34507306-fJYSoMdju3Vv9SecfdyCUbYu5JdlIPLyaVN3xElNw, oauth_consumer_key=FFUZwLopTkug9Dlj1KamA, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274396737, oauth_nonce=571291495191528, oauth_version=1.0, oauth_signature=CqiI%2FY%2Br96PGVPkCSClqnkmfHAo%3D Transfer-Encoding: chunked Host: api.twitter.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.0 (java 1.5) Expect: 100-Continue status=Testing+oacurl[\n] -- Richard
[twitter-dev] Re: Mobile OAuth Summary
On Apr 30, 5:52 pm, bob.hitching b...@hitching.net wrote: At Xumii we’re using Twitter mobile oAuth on a wide range of phones, from low-end feature phones to high-end smartphones. A recent QA cycle revealed 7 out of 30 Most Popular devices not coping with Twitter mobile oAuth: Samsung C3110, Nokia 3120, SE G502, SE C905, LG KU990, Nokia N96, SE W705. Our Xumii products would also benefit from MobileOK-compliant protected Twitter account pages on m.twitter.com or mobile.twitter.com. I raised this in http://groups.google.com/group/twitter-development-talk/browse_frm/thread/f41e4299a646520b but there was no resolution. -- Richard
[twitter-dev] Re: Mobile view of twitter.com doesn't show This person has protected their tweets message
On Apr 8, 1:41 am, Abraham Williams 4bra...@gmail.com wrote: Have a look at the new http://mobile.twitter.com. It looks awesome and displays if profiles are protected. It does look awesome; unfortunately it uses a bunch of Javascript which (in general) many low-end mobile browsers can't handle. I need a mobile-optimised Javascript-free page that displays the protected message. -- Richard
[twitter-dev] Mobile view of twitter.com doesn't show This person has protected their tweets message
For the case where I'm trying to view a protected Twitter account profile http://twitter.com/username I'm not signed in or not a follower: - Standard view displays a page with a lock image the message This person has protected their tweets - Mobile view displays a page with a message This functionality is not currently supported in the mobile site. This is coming soon. Thanks for your patience! This occurs in FF, IE, Chrome Opera. This is confusing to users of the app I'm developing, which renders a mobile-optimised webpage with links to http://m.twitter.com/username. Is this likely to be fixed any time soon? Thanks -- Richard Barnett -- To unsubscribe, reply using remove me as the subject.
