77tontos
- 88tontos
- 88tontos@gmail.com
- Europe/Stockholm
- Yes
- No
1 issues
Key
Summary
Status
Reporter
Assignee
Created
WEB-1444Changed Description:
[Tweet saying the api services were restored|https://twitter.com/MojangStatus/status/1175921587108925440?ref_src=twsrc%5Etfw%7Ctwcamp%5Eembeddedtimeline%7Ctwterm%5Elist%3AMojang%3Amojang_help%7Ctwcon%5Etimelinechrome&ref_url=https%3A%2F%2Fhelp.mojang.com%2F]
Example request
curl -X POST \ https://api.mojang.com/profiles/minecraft \ -H 'Accept: */*' \ -H 'Accept-Encoding: gzip, deflate' \ -H 'Connection: keep-alive' \ -H 'Content-Length: 27' \ -H 'Content-Type: application/json' \ -H 'Host: api.mojang.com' \ -H 'User-Agent: PostmanRuntime/7.17.1' \ -d '[ "notch","Garbagiozo" ]'Response Code 403
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD> <BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Request blocked. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: PwM7rheAN9fvbxxYrhzKoSbco1U8NtYQk0z-aLjBLB6RbU9a_6HEQg== </PRE> <ADDRESS> </ADDRESS> </BODY> </HTML>
@MojangStatus on twitter tweeted that the services were back online but thats not true for all requests.
The requests are not going through on our Minecraft servers or on any of our developers home connections so I know its not an ip ban.
Example request
curl -X POST \ https://api.mojang.com/profiles/minecraft \ -H 'Accept: */*' \ -H 'Accept-Encoding: gzip, deflate' \ -H 'Connection: keep-alive' \ -H 'Content-Length: 27' \ -H 'Content-Type: application/json' \ -H 'Host: api.mojang.com' \ -H 'User-Agent: PostmanRuntime/7.17.1' \ -d '[ "notch","Garbagiozo" ]'Response Code 403
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD> <BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Request blocked. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: PwM7rheAN9fvbxxYrhzKoSbco1U8NtYQk0z-aLjBLB6RbU9a_6HEQg== </PRE> <ADDRESS> </ADDRESS> </BODY> </HTML>
I have a few players who are not able to migrate due to the emails not being valid.
Name MC only knows the accounts you give it. When an inactive player types in their name for the first time or joins a public server prompting someone else to do it than it is added to the list of known capes. No specific api call exists that will return a list of all the capes in existence.
Another possible cause is those who never have the cape equipped will not show with a cape either. However once you equip it and lookup your name, Name MC will than forever cache it.
The last and only reason which is much more unlikely is the one stated above. Surprisingly some never redeem their code.
I noticed this a few months ago, seeing as this documentation is not directly provided by Mojang its very possible it has changed. I just cache the information I need from the authenticate request which returns all the same info. I would question why you need most this information though as a lot of it is irrelevant to Minecraft itself.
No I was unaware of it being private. As of this morning it appears to be working again.
I don't seem to see a resolved button.