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.
12Next page
 

api.testeveonline.com is back online

First post
Author
Previous Topic Next Topic
CCP illurkall
C C P
C C P Alliance
#1 - 2012-11-13 11:09:40 UTC
Hey there

We just re-enabled https://api.testeveonline.com/ on top of Singularity. The changes we are introducing now are:
- gzip is enabled for all XML endpoints
- Removed uneccessary IIS and .net related HTTP headers
- Removed the cache-control header (now that we are on https only there is no way to cache responses on proxies anyway)
- This was causing issues for some VBA code in Excel
- Replaced the underlying distributed cache service (shouldn't affect anything but please report to this thread if you notice anything weird, we need to fine-tune how much resources we allocate on the caching layer for Singularity and we are starting small)

We'll run this on Singularity for a while and if all goes well deploy to TQ shortly.
Desmont McCallock
#2 - 2012-11-13 14:39:12 UTC
Usually the test API server was reachable through https://apitest.eveonline.com and the corresponded keys where issues through https://supporttest.eveonline.com/

What happened to that? (Not to mention that some of us devs have our apps already configured to that addresses).
CCP illurkall
C C P
C C P Alliance
#3 - 2012-11-13 15:36:38 UTC
We want to limit the .eveonline.com domain for production applications running on Tranquility going forward. https://api.testeveonline.com is now running on infrastructure setup that is similar to what is used in production and we used the opportunity to change the domain as well.
At the moment we have not configured a support site for SISI for generating new API keys, the API key database is about a week old backup of the live one (at the time of this post).
Lors Dornick
Kallisti Industries
#4 - 2012-11-13 15:54:00 UTC
CCP illurkall wrote:
We want to limit the .eveonline.com domain for production applications running on Tranquility going forward. https://api.testeveonline.com is now running on infrastructure setup that is similar to what is used in production and we used the opportunity to change the domain as well.
At the moment we have not configured a support site for SISI for generating new API keys, the API key database is about a week old backup of the live one (at the time of this post).

+1 for letting us have access to the test api.
+2 for not letting anything mess with the production applications.

CCP Greyscale: As to starbases, we agree it's pretty terrible, but we don't want to delay the entire release just for this one factor.
Karbowiak
State War Academy
Caldari State
#5 - 2012-11-13 19:06:14 UTC  |  Edited by: Karbowiak
- Replaced the underlying distributed cache service

wat, does this mean that multiple sites can access killlog from the same char/account, WITHOUT generating an error?
If yes, then amazeballs! Lol

also, yay gzip \o/

edit://
illurkall, you should come by IRC - #eve-dev - pretty sure alot of people would love you if you did that
Squizz Caphinator
The Wormhole Police
#6 - 2012-11-13 19:09:24 UTC
CCP illurkall wrote:

- gzip is enabled for all XML endpoints


Awesome!

CCP illurkall wrote:

- Replaced the underlying distributed cache service (shouldn't affect anything but please report to this thread if you notice anything weird, we need to fine-tune how much resources we allocate on the caching layer for Singularity and we are starting small)


Does this mean that two separate killboards attempting to retrieve the KillLog for the same api won't interfere with each other anymore? Today, it is a race between killboards. If a user provides their KillLog enabled API to two killboards, one of them will get a 119 error. If you'd like a more detailed explanation or example let me know.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com
Desmont McCallock
#7 - 2012-11-13 21:11:24 UTC  |  Edited by: Desmont McCallock
And KillLog is not the only defected API call, but it is the most severe one. Bug reports have been submitted for several API call defects in the past, you may wonna have a look at them.

Edit: After doing a test on test API server, KillLog call still behaves as before.
CCP illurkall
C C P
C C P Alliance
#8 - 2012-11-13 21:51:06 UTC
Confirming KillLog is not fixed in this update Sad
The cache server change is internal only and shouldn't have any effect on functionality.
xHjfx
The Legion of Spoon
Curatores Veritatis Alliance
#9 - 2012-11-13 23:36:46 UTC
CCP illurkall wrote:
We want to limit the .eveonline.com domain for production applications running on Tranquility going forward. https://api.testeveonline.com is now running on infrastructure setup that is similar to what is used in production and we used the opportunity to change the domain as well.
At the moment we have not configured a support site for SISI for generating new API keys, the API key database is about a week old backup of the live one (at the time of this post).


Legendary, thanks for your work and keeping to your word ^^
Squizz Caphinator
The Wormhole Police
#10 - 2012-11-14 16:31:25 UTC
CCP illurkall wrote:
Confirming KillLog is not fixed in this update Sad
The cache server change is internal only and shouldn't have any effect on functionality.


Bummer. Thank you for letting us know though.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com
Peter Powers
Terrorists of Dimensions
HORSE-KILLERS
#11 - 2012-11-14 19:49:55 UTC
so where is the CREST test server?

3rdPartyEve.net - your catalogue for 3rd party applications
Desmont McCallock
#12 - 2012-11-14 21:35:27 UTC
Peter Powers wrote:
so where is the CREST test server?

Peter, you are asking the wrong person.
Dei
Cosmic Core Industries
#13 - 2012-11-14 23:44:58 UTC
Is it possible to request that all long cache api test calls are changed to short cache? I'm sure I'm not the only one that loves to traverse xml with guess work and get a once per day chance to see if we've got it right!
CCP illurkall
C C P
C C P Alliance
#14 - 2012-11-15 11:15:06 UTC
At the moment we are using the TQ cache timeouts on SISI. I agree that for testing purposes the cache timeouts should be shorter.
I will make it so.
Dei
Cosmic Core Industries
#15 - 2012-11-15 18:23:38 UTC
Oh cool, thanks. I was expecting you to say 'no'. Big smile
Karbowiak
State War Academy
Caldari State
#16 - 2012-11-15 21:48:45 UTC  |  Edited by: Karbowiak
So, we decided to implement our own gzipping and caching, mostly as a test (but also because we got titillated by the prospect of gzip)

http://5.44.237.39 is transparent proxying all API calls from the TQ API server, with full transparent caching of calls (it's stored internally for the duration that the API specifies) and it's fully gzipped - no ssl tho, too lazy to fix that.

We are currently using it full on for EVE-KILL, and are seeing roughly 90% bandwidth savings, and an increased throughput for our cronjobs.

So, yeah, we're looking forward to gzip being enabled, VERY MUCH! Then we can skip atleast one level of our setup.
Oh and, anyone interested in using our proxy, go for it :)

edit://
if anyone wants the code, i'll upload it somewhere so you can look at it, we use Varnish for frontend stuff (including gzip) and golang for the http/proxy/caching part together with memcached (for the storage)
Desmont McCallock
#17 - 2012-11-16 07:49:00 UTC  |  Edited by: Desmont McCallock
Karbowiak wrote:
...and golang for the http/proxy/caching part together with memcached (for the storage)

Related to using memcached, I just discovered Couchbase which is memcached compatible with better monitoring app and many more features. Truly worth looking at.
Squizz Caphinator
The Wormhole Police
#18 - 2012-11-16 21:06:49 UTC
Here's a visual representation of when we switched to our gzipp'ed proxy:

http://i.imgur.com/xmnGU.png

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com
Desmont McCallock
#19 - 2012-11-18 13:14:58 UTC
Support for compressed responses has been added in EVEMon's code base. Will be available with the next release, probably shortly after the 'Retribution' expansion.
Confirming that everything works as intended.
Dei
Cosmic Core Industries
#20 - 2012-11-18 23:11:23 UTC
The gzipped responses are working fine for me using Nodejs, and original functionality hasn't been affected either.
12Next page