As of yesterday, May 17, I've been unable to get request tokens to
login via the API for my web-based Twitter client.

Now, whenever I try to get a request token, I get a 401 HTTP code,
"Failed to validate oauth signature and token"

The url in question:
The app is called "Tim's Home Page"

I've tried resetting the API keys, made sure all the API urls were
pointing to the correct locations, and still haven't been able to fix
the problem.

Normally, I'm able to connect either through an @anywhere bridge code,
or directly using the REST api.

I'm using the TwitterOauth library, and that calls to

I know the bridge code isn't supported, but that's a secondary issue
at this point.

Also, I was able to connect reliably prior to May 17. I hadn't changed
any of my login code when I started having the issue.

These are the headers of the response:
[http_header] => Array
            [date] => Wed, 18 May 2011 19:48:44 GMT
            [server] => hi
            [status] => 401 Unauthorized
            [x_transaction] => 1305748124-55771-54144
            [x_frame_options] => SAMEORIGIN
            [last_modified] => Wed, 18 May 2011 19:48:44 GMT
            [x_runtime] => 0.00721
            [content_type] => text/html; charset=utf-8
            [content_length] => 44
            [pragma] => no-cache
            [x_revision] => DEV
            [expires] => Tue, 31 Mar 1981 05:00:00 GMT
            [cache_control] => no-cache, no-store, must-revalidate,
pre-check=0, post-check=0
            [x_mid] => 48d06356e9a0e07c6cf92e22490f158add0e21b5
            [set_cookie] =>
e54173a833746ed6ab7a99af5fae672a63223f55;; path=/;
            [vary] => Accept-Encoding

The body of the response is "Failed to validate oauth signature and

To get the response, I'm using the TwitterOauth library, which
accesses this url via a GET request:

(Obviously the timestamp sent is different based on the request)

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:!forum/twitter-development-talk

Reply via email to