No jsonp support about api.minetools.eu HOT 11 CLOSED

Https did the trick, thank you.

from api.minetools.eu.

Hi,

why do you need jsonp?
MineTools supports Cross-Origin Resource Sharing. That should be enough these days.

from api.minetools.eu.

Well, my browser says, no access-control-allow-origin header in your server response. That problem appeared about two months ago, i think. So i thought something changed in api policy.

from api.minetools.eu.

What browser and version do you use?

I do see that header in my browser.

from api.minetools.eu.

That is chrome for linux.

from api.minetools.eu.

You should try updating it to the latest version.
I don't really understand why you shouldn't have the header because it is definitely there.

from api.minetools.eu.

Strange. Probably this's a bug (or feature) with legacy angularjs's $http service, because i have reports about the same code working in other people's chrome browsers sometimes. Probably some security updates for legacy version have appeared throw cdn.
I think i'll need some more time to deal with this. Thanks for quick answers, anyway.

from api.minetools.eu.

Which chrome version are you running? I just tried your application and it works fine for me.

I'm running chrome Version 52.0.2743.116 m

from api.minetools.eu.

My version is 53.0.2785.92 (64-bit), but i have this problem in any browser, if i use my angular app. If i access api directly, everything ok with headers. I just thought you've stoped responding cross-domain requests when i saw browser became to block requests. So it's my-side problem, i think.

from api.minetools.eu.

Hmm that's really weird. You could try to use the https URL to connect to the API because you save the redirect from http zu https then.

from api.minetools.eu.

Awesome. I also just added the CORS header to the redirect from http to https. Never knew that is required.

Thanks for reporting that issue.

from api.minetools.eu.