These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

@foxfour - Illegal Page requests
Author
Previous Topic Next Topic
insidious Evils
East Khanid Trading
#1 - 2015-02-14 00:02:27 UTC  |  Edited by: insidious Evils
Hi.

this post is mainly directed at Foxfour. Not so long ago, i made a post here regarding random illegal page requests.

When i mean random i mean, if i call a request to say the charsheet using an API key it can generate the illegal page error, but the next time it is called it doesn't .....

I have been logging these errors. here is an example with the API data masked

Illegal page request! Please verify the access granted by the key you are using!(https://api.eveonline.com/char/CharacterSheet.xml.aspx?keyID=xxxxxx&vCode=xxxxxxx&characterID=xxxxx)
If i copy the actual API URL and pasted it into the browser, it works fine.

My main concern is the number of these i am getting. Over just a few days i have generated about 150 of them now. And i am lead to believe that these errors count towards my error allowance so to speak. My script obeys cache timers and i have used a 1 sec sleep to test if the error is a flood issue, and it has had no effect on the number of errors i generate.

Is foxfour aware of this issue and how in danger am i of having the IP address used blocked ?

Yours
Insid
Dragonaire
Here there be Dragons
#2 - 2015-02-14 21:15:18 UTC
If you are sure you are obeying the cache times I wouldn't worry about it there are times when the API servers do return errors but resenting the same request is fine. I've been working with the Eve API servers for over 5 years now and it seems to be something they just do from time to time and if it would get you banned they'd done so long ago with me Blink. What could be causing it might not even be on your end or CCP's but something wrong in the middle and they just error out by default. Also just to be clear most of CCP's limit are of the per min type and just result in temp bans and they would return a different error code so if you handle them correctly you can insure you know when something goes wrong. In the library I wrote (Yapeal) any errors of those type cause it to ignore the included cache times and and use a 24 hour one instead. I also use 5 min timer on ones like you describe because I know in 99.99% of the time they will go through when resent but don't want to cause to many problems in case it is something from my end. If you are true concerned about it make sure you sent a user agent header with enough info they can contact you if they have concerns in what they are see. As they have stated they will try to contact you before they do a permanent band if it's possible.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.