EVE Technology Lab

Forum Index

EVE Forums » EVE Technology and Research Center » EVE Technology Lab » Help with API requests

Topic is locked indefinitely.

Help with API requests
Author

Previous Topic Next Topic

insidious Evils

East Khanid Trading

Likes received: 0

#1 - 2015-01-12 21:08:17 UTC | Edited by: insidious Evils

Hi all.

I am getting random illegal page requests 221, check the key access..... However, running the query manually works fine. I am mainly getting this error for starbase details, however i got it for corp contracts today as well. I thought it might be a flood issue, but i put a 1 second sleep between pulls to ensure that i am waiting and i am still getting them. The errors are random, not normally the same calls so its not the same towers for example with starbase details. I am obeying cache timers and data is pulled as soon as the timer expires. The script runs every 5 mins. Out of all of the calls in a 24 hour period i am getting about 6-8 errors, which is also pretty random, meaning 97% of the time the call works.......

Anyone else getting this and can shad some light.

cheer
evils

salacious necrosis

Garoun Investment Bank

Gallente Federation

Likes received: 38

#2 - 2015-01-12 23:01:03 UTC

I haven't asked WHY this happens, but I see the same thing. Some days I see zero errors, other days I see a handful. My site makes ALL of the available API calls, but I only make them once every 20 minutes, so I may be seeing a different pattern than you. It's hard at the moment for me to get comparable stats as some of the accounts on my site have let their keys expiry. However, on the accounts I control, I only see a handful of these (for calls which should normally work).

So...you're not crazy :)

Use EveKit ! - Tools for EVE Online 3rd party development

Ydnari

Estrale Frontiers

Likes received: 435

#3 - 2015-01-12 23:47:23 UTC

It's done it for months, even with proper rate limiting and everything.

https://forums.eveonline.com/default.aspx?g=posts&t=331824
https://forums.eveonline.com/default.aspx?g=posts&t=357617

I no longer trust the 221 error, particularly since phealng does a pretty solid job of validating permissions up front so it's very unlikely to be a genuine 221 (someone would have had to have changed key permissions and a request made in the period when the key info is still cached - not a very big window).

So I treat 221 as a transient failure, ignore the cache timer and retry in 1 hour instead of the 24 hours it says - this pretty much always works, since it's always this false failure, whilst still slowing down since clearly something in the API is broken.

I've got 81 occurrences of this in my logs since 2014-12-18.

Association of Commonwealth Enterprises 2
Smallevils Association of Commonwealth Enterprises Likes received: 2	#4 - 2015-01-14 11:30:45 UTC Hi guys. Thanks for your replies. I will continue to log these errors but will pretty much ignore them. As they are fairly rare, and my calls are generally not time sensitive i can live with the odd missed update due to the 221s. Hopefully Foxfour is aware of this and a fix will appear in due course. again, thanks for your assistance. Evils

qu1ckkkk

The Warp Core Stabilizers

Likes received: 36

#5 - 2015-01-14 15:55:31 UTC | Edited by: qu1ckkkk

Be careful if you start to make large volumes of calls. Even though these 221's are occurring for ~reasons~, they still count towards your error threshold and will get your IP temp/perma banned if they happen too often. I have seen a number of cases with very large SeAT installs reporting this behavior.

Proud developer of SeAT! A Simple Eve API & Corporation Management Tool.

Project Page: https://github.com/eveseat/seat