Hi, Thanks for the advice once again. I've spent the day porting it over to visual studio for more flexibility and to use the example you provided as a guide. After following the gist of what the other .net user had done, I'm still experiencing the rate limit issue. I'm toying with creating an authorization header, but what value does your API take for that and in what format (i.e. username:password or such)?
Any help you could provide would be greatly appreciated. Thanks for your time, DuBose On Apr 23, 6:12 pm, Matt Sanford <[email protected]> wrote: > Hi there, > > The username:password in the URL is a shortcut but it sounds like > the VBA library is ignoring it. Well, is stripping it and not creating > and Authorization header. There is no way to specify these later in > the URL. If the library lets you set headers you could try generating > the Authorization header yourself, but outside of that I'm not aware > of any work around. > > Thanks; > – Matt Sanford / @mzsanford > Twitter API Developer > > On Apr 23, 2009, at 09:57 AM, DuBose Cole wrote: > > > > > Hi Matt, > > Thanks for such a quick response, I really appreciate the help. I > > think the way I'm using vba (kicking myself for not actually starting > > the project explicitly in .net/visual studio), my method won't allow > > the last workaround used. If I can ask, in the URL that is submitted > > to the REST API, I'm currently quering using my login and password in > > the following format: "Http://username:passw...@twitter.....", is > > there a way to include these as parameters later in the URL? After > > taking your suggestion and using Charles, I can see that the account > > details aren't being transferred wtih the rest of the URL to your API > > and thought if there is another place your API accepts it, I could use > > it as a workaround. > > > Any help you could provide would be great as I've become slightly > > invested in the way I've created it so far and would hate to scrap > > parts and redo it. > > > Thanks, > > > DuBose > > > On Apr 23, 4:14 pm, Matt Sanford <[email protected]> wrote: > >> Hi DuBose, > > >> The account looks whitelisted. The most common issue when using > >> authenticated requests is that you're calling a method that does not > >> require authentication and your HTTP library is not sending it. I > >> have > >> seen some reports of this with .NET languages. Take a look at this > >> old > >> discussion and see if it helps: > > >> http://groups.google.com/group/twitter-development-talk/browse_thread > >> ... > > >> If not you might want to try using a proxy like Charles [1] so > >> you can verify the requests are being sent with an Authorization > >> header. > > >> Thanks; > >> — Matt Sanford > > >> [1] -http://www.charlesproxy.com/ > > >> On Apr 23, 2009, at 08:02 AM, DuBose Cole wrote: > > >>> I was wondering if anyone else has encountered problems with the > >>> rate > >>> limit while whitelisted. I recieved whitelisting authorization for > >>> my > >>> app development, but my rate still shows up as 100 per hour. After > >>> running into this problem and reading about some database issues a > >>> while back, I applied again, got accepted and have encountered the > >>> same issue. I'm making authenticated calls in my code using my white > >>> listed id (@dubosecole). I'm using basic authorization and not > >>> OAuth, > >>> are there any other steps anyone can suggest? > > >>> I'm using it for network visualization/message transmission analysis > >>> rates in a relatively simple vba package and this rate limit issue > >>> is > >>> seriously slowing down development. > > >>> Any help anyone can provide would be appreciated. > > >>> Thanks, > > >>> DuBose
