Askur
Askur
Got the clarification back and GD is happy to provide this out of client on a 24 hour delay to avoid facilitating automatic detection of things.
I´ll see if I can get the GD people to come over here and have a discussion about this.
Functional Parity will be maintained for pre-existing calls.
Mental Note: This has to be alliance AND corp, not just corp and then a separate one for alliances because any corp in an alliance will always be registered into...
I am terrible with closing these issues or assigning them elsewhere! Pretty sure I addressed this in the monolith a long time ago and such.. let me look over code...
There's totally changes to factor in alliance membership for corps, on the 20th of June.
All monolith side stuff seems on the up and up for this but I can't find an ESI action using this, nor is it on the current XML Parity list....
These 420 errors are actually just the monolith action wrappers picking up a error being scattered back to the client making the call. We call them UserErrors and they are...
But we totally know what went wrong, it´s a part of the message and ESI does get that message sent as a response to the action, marked as a 420...
ESI can actually see from the response it gets back from the monolith what the reason for the failure is. I never really intended the 420 status codes to leave...