[twitter-dev] Search API throwing an error when no user-agent defined

[Marsh Gardiner]

Here's a strange issue… When I use the Apigee API Console to make a request, 
it throws a 400 Bad Request error 
(example),
 
unless I define the User-Agent header 
(example).
 
This seems to happen on our production boxes but not on our dev/qa 
machines. 

The only difference between those setups is that prod is whitelisted, though 
I wouldn't expect that to affect the search API in any way. Any ideas what's 
happening? 

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: New API Console & Documentation updates on dev.twitter.com

[Marsh Gardiner]

Whoops, I put percent-encoded on text of the web intent link where it wasn't 
necessary.

Feedback tweeted @apigee  is 
the proper way to send it.

-- 
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: New API Console & Documentation updates on dev.twitter.com

[Marsh Gardiner]

We (I work at @apigee) are refreshing the WADL 
description
 that 
drives the API Console for Twitter in the next few days to make sure that it 
is as up-to-date as possible.

And if anyone has feedback about what would make the API Console better for 
them, please send us a tweet or 
reply here.

-- 
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: garbage in json api response?

[Marsh Gardiner]

I see it too. Here's a cached version of the response:
http://app.apigee.com/console/apigee-console-snapshots-128331720_b7a1fe22-6ec8-4996-ba1a-2720227c896c/rendersnapshotview

The same request with xml seems to be working fine:
http://app.apigee.com/console/apigee-console-snapshots-128331720_66477219-251e-401e-8c74-f16e2a504483/rendersnapshotview

-- 
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] Re: oauth echo php sample

[Marsh Gardiner]

Not sure how much this would help you, but you can see any header that
has been sent via Apigee's test console via the request tab.

http://app.apigee.com/console/twitter

If there's more information you'd like to see in there, do let us
know, as we're always working to improve the test console.

Marsh

On Sep 1, 8:02 pm, sdenike  wrote:
> Does anyone have a sample header that should be sent back to twitter
> as well as maybe the curl commands?  I have been trying to construct a
> header to send back to twitter using OAuth echo, but have not been
> successful in doing so.  And example would be excellent if anyone is
> able to provide.  Thanks

-- 
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] Re: Using oAuth by Curl

[Marsh Gardiner]

You might try Apigee's test console for the Twitter API:
http:/app.apigee.com/console/twitter

If you do, let us know how it works for you. We're always interested
in feedback on how to make it better!

Thanks,

Marsh

On Sep 1, 10:36 pm, Andrea Stagi  wrote:
> Hi,
>
> I'm developing a twitter client using curl...Yesterday twitter closed
> the basic authentication, replacing it with oAuth..I really need help
> for it! I have to convert my application now, I tried to use twurl but
> I receive this error:
>
> /var/lib/gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/
> authorization_controller.rb:2: uninitialized constant
> Twurl::AbstractCommandController
>
> An application's bug? An error of mine?
>
> There are any alternatives??
>
> Thank you all...
>
> p.s. I've just registered my application, so I have all keys needed...

-- 
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