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.
 

[ESI] Warning headers : what do they look like ?
Author
Previous Topic Next Topic
YeuxVerts Belle
Royal Amarr Institute
Amarr Empire
#1 - 2017-02-19 04:47:27 UTC
Hi,

I've started moving away from XML and CREST to ESI, and i've taken note of the existing versioning system. I understand all of it, except how to find the warning headers when i call a legacied route. Can anyone shed some light on this? Are they HTTP headers, and if so, which ones?

I've queried https://esi.tech.ccp.is/v1/alliances/99000054/ (legacy) and https://esi.tech.ccp.is/v2/alliances/99000054/ (latest) on SoapUI, but i don't see any difference besides the renamed executor corp.

The above message presents my opinions on the topic at hand. If there is a conflict between my views and reality, consider reality to be correct until proven otherwise.
Blacksmoke16
Resilience.
#2 - 2017-02-19 05:14:09 UTC
It's an HTTP Header called warning. If it doesn't show up then that means that endpoint is still valid. You can see an example of it by calling the /legacy/ version and viewing the headers in Postman or similar app.

https://esi.tech.ccp.is/legacy/alliances/99000054/ 

warning →299 - This endpoint was deprecated on 2016-10-01.
YeuxVerts Belle
Royal Amarr Institute
Amarr Empire
#3 - 2017-02-19 05:37:36 UTC
Blacksmoke16 wrote:
warning →299 - This endpoint was deprecated on 2016-10-01.

Saw it in SoapUI. Thanks.

Blacksmoke16 wrote:
https://esi.tech.ccp.is/legacy/alliances/99000054/

How come i get the warning with legacy and not with v1, since v1 is legacy in this case?

The above message presents my opinions on the topic at hand. If there is a conflict between my views and reality, consider reality to be correct until proven otherwise.
Blacksmoke16
Resilience.
#4 - 2017-02-19 14:50:23 UTC
Dunno.
Daneel Trevize
Give my 11percent back
#5 - 2017-02-19 15:05:04 UTC
Possibly because v1 is the latest, so there is no true legacy version, but all calls to /legacy/ are configured to spit out the warning?
YeuxVerts Belle
Royal Amarr Institute
Amarr Empire
#6 - 2017-02-20 08:56:03 UTC
Daneel Trevize wrote:
Possibly because v1 is the latest, so there is no true legacy version, but all calls to /legacy/ are configured to spit out the warning?


In tihs case, v1 is legacy and v2 is latest.

The above message presents my opinions on the topic at hand. If there is a conflict between my views and reality, consider reality to be correct until proven otherwise.