Releases: eveseat/eseye
v2.2.0
This version address an issue with cache system and EsiResponse container serialization.
Previous versions were not building proper serialized object when response was containing an array. As a result, cached response was not usable and Eseye need to sent a new request even if content didn't expires.
Cache based on ETag response have been improved aswel to update internal content instead sending requests continuously.
Be sure you are clearing cache after this update as existing content will non longer be valid.
v2.1.1
v2.1.0
Enhancement
This version is dropping OAuth v1 endpoints to the new v2 implementation and use JWT token mechanics.
Existing v1 tokens are automatically converted into v2 format on first call.
ESI is configured to use either one or the other version - so no impact is intended.
To sign and check provided token, you'll need the following extensions on your installation :
- gmp
- mbstring
- openssl
v2.0.0
v1.1.8
feat(core): Allow Eseye to use alternative SSO endpoint (#47) CCP is working hard to make Tranquility ESI compliant together with Serenity reborn. According to CCP Bartender, they're targetting a maximum of 48 hours delay between Tranquility updates and Serenity updates. In despite that we already allow alternative ESI and source endpoints, we're still use hardcoded SSO endpoint which is not possible with Serenity Architecture. Base ESI would be https://esi.evepc.163.com and the OAuth path should be https://login.evepc.163.com (according to actual documentation) Closes eveseat/seat#550
