Abraham,
Thank you for your suggestion about curl http://jazzychad.net/iponly.php;.
Submitting the IP produced by this command seem to have fixed our rate
limit issue.
Thank you,
-Stas
On Dec 13, 8:48 pm, Abraham Williams 4bra...@gmail.com wrote:
Depends on on your server setup. You might have
If your whitelisted ip is w.w.w.w and outgoing interface is o.o.o.o
For any request twitter will see o.o.o.o as your ip address. Not w.w.w.w
if you have w.w.w.w interface attached to your host and its an
Internet gateway but not the default gateway (o.o.o.o) you can bind
all the twitter connection
Thanks Abraham,
Does this mean that the IP produced by traceroute http://myservername.com;
was an incorrect one?
Thank you,
-Stas
On Dec 11, 12:36 pm, Abraham Williams 4bra...@gmail.com wrote:
Make sure you got the correct IP whitelisted.
From your server do
Depends on on your server setup. You might have different IPs depending on
weither the request is incoming or outgoing.
A sure fire way to check though is to compare them.
Abraham
On Sun, Dec 13, 2009 at 12:48, Stas stas.ant...@gmail.com wrote:
Thanks Abraham,
Does this mean that the IP
Hi Michael,
Thanks you for your response.
The error does not specify the reason (see below), but it does show
when 'get status' method is being executed for an user ID that is has
not been whitelisted; we cannot possibly whitelist all application
users.
ERROR: Rate limit exceeded. Clients may not
