I would recommend just using a physical server and uploading a simple php proxy script. If you have existing webspace, it will save you the trouble of setting up an complete ec2 build just to run a proxy script.
On Oct 9, 7:11 pm, Akshar <[email protected]> wrote: > Thanks Abraham. > > Any pointers on how to setup a proxy on amazon ec2 for GAE? > > On Oct 8, 6:07 pm, Abraham Williams <[email protected]> wrote: > > > Pretty much. You have limited options: > > 1) Run your Search API requests through a proxy where you will have > > exclusive access to the IP. > > 2) Wait for V2 of the Twitter API where the REST and Search APIs get > > combined so you can have authenticated search queries. > > 3) Hope Twitter slaps some duct tape on the issue and rolls out a > > whitelisting method for the Search API that includes passkeys in your user > > agent or some such thing. > > 4) Develop on non cloud base infrastructure. > > 5) Something else. > > > Abraham > > > 2009/10/8 Akshar <[email protected]> > > > >http://apiwiki.twitter.com/Rate-limitingstatesthat "for cloud > > > platforms like Google App Engine, applications without a static IP > > > addresses cannot receive Search whitelisting." > > > > Does that mean there is no way to avoid getting HTTP 503 response > > > codes to search requests from app engine? > > > > On Oct 8, 2:09 pm, Akshar <[email protected]> wrote: > > > > Any other solutions available for app engine folks stuck out here? > > > > Please help! > > > > > I'm noticing this exact problem as well. I'm making only a few > > > > requests per hour. I have tried setting the user-agent but it did not > > > > help. > > > > > Akshar > > > > > On Oct 6, 9:50 am, Chad Etzel <[email protected]> wrote: > > > > > > Hi All, > > > > > > GAE sites are problematic for the Twitter/SearchAPIbecause the IPs > > > > > making outgoing requests are fluid and cannot as such be easily > > > > > allowed for access. Also, since most IPs are shared, other > > > > > applications on the same IPs making requests mean that fewer requests > > > > > per app get through. > > > > > > One work around would be to spin up a server in EC2 or Rackspace Cloud > > > > > or something and use it as a proxy for your requests. That way you > > > > > have a dedicated IP that will have its full share of resources talking > > > > > with the Twitter servers. > > > > > > HTH, > > > > > -Chad > > > > > > On Tue, Oct 6, 2009 at 12:45 PM, Martin Omander <[email protected]> > > > wrote: > > > > > > > Same here; my app runs on Google App Engine and 40% of the requests > > > to > > > > > > the TwitterSearchAPIget the 503 error message indicating rate > > > > > > limiting. > > > > > > > Is there anything we as app authors can do on our side to alleviate > > > > > > the problem? > > > > > > > /Martin > > > > > > > On Oct 5, 1:53 pm, Paul Kinlan <[email protected]> wrote: > > > > > >> I am pretty sure there are custom headers on the App Engine that > > > indicate > > > > > >> the application that is sending the request. > > > > > > >> 2009/10/5 elkelk <[email protected]> > > > > > > >> > Hi all, > > > > > > >> > I am having the same issue. I have tried setting a custom > > > user-agent, > > > > > >> > but this doesn't seem to affect the fact that twitter is limiting > > > > > >> > based on I.P. address. I'm only making about 5 searches an hour > > > and > > > > > >> > 80% of them are failing on app engine due to a 503 rate limit. > > > > > >> > Twitter needs to determine a better way to let cloud clients > > > access > > > > > >> > theirsearchAPI. It seems like they have really started blocking > > > > > >> >searchrequests in the last week or so. > > > > > > >> > If anyone has any idea about how to better identify my app engine > > > app > > > > > >> > please let let me know. > > > > > > >> > On Oct 5, 2:59 am, steel <[email protected]> wrote: > > > > > >> > > Hi. I have this problem too. > > > > > >> > > My application does two request per hour and it get "rate > > > limit". > > > > > >> > > What is wrong? I think it is twitter's problems.... > > > > > > >> > > On 1 окт, 01:45, Paul Kinlan <[email protected]> wrote: > > > > > > >> > > > Hi Guys, > > > > > >> > > > I have an app on the App engine using thesearchAPIand it is > > > getting > > > > > >> > > > heavily rate limited again this past couple of days. > > > > > > >> > > > I know that we are on a shared set of IP addresses and > > > > > >> > > > someone > > > else > > > > > >> > could be > > > > > >> > > > hammering the system, but it seems to run for weeks without > > > seeing the > > > > > >> > rate > > > > > >> > > > limit being hit and then all of a sudden only about 60% of > > > > > >> > > > the > > > searches > > > > > >> > > > I perform will be rate limited. This seems to occur every > > > > > >> > > > two > > > months > > > > > >> > or so. > > > > > > >> > > > Has something changed recently? > > > > > > >> > > > Paul > > > -- > > Abraham Williams | Community Evangelist |http://web608.org > > Hacker > > |http://abrah.am|http://twitter.com/abrahamhttp://web608.org/geeks/abraham/blogs/2009/... > > This email is: [ ] blogable [x] ask first [ ] private. > > Sent from Madison, WI, United States > >
