Help with Javascript and Github Pages

[RGBKey]

Hello, I was trying to make a site that would display API data from multiple exchanges and display it to the user as a learning project but when I went to actually use javascript to get the API data, my IP was blocked from Bitstamp's servers. I assume this is because someone on github pages went over the request limit and got the IP banned. Is there a way to make the javascript send the request from the client IP instead of the server so that the IP isn't blocked? Thanks!

[1715234029]

1715234029

[1715234029]

1715234029

[1715234029]

1715234029

[1715234029]

1715234029

[1715234029]

1715234029

[9inety7even]

If you're using something like jQuery.get() then it's already sending it from the client IP.

[scribe]

Are you authenticating with the bitstamp API properly? Not used it myself but the doc page says all requests need to be authenticated.  Or are you seeing a message specifically relating to limits?

[RGBKey]

Are you authenticating with the bitstamp API properly? Not used it myself but the doc page says all requests need to be authenticated.  Or are you seeing a message specifically relating to limits?

I'm using the public part (https://www.bitstamp.net/api/ticker/) so it doesn't need authed per the docs. On my webpage with jQuery, I opened the console and did this:

Code:

var test = jQuery.getJSON("https://www.bitstamp.net/api/ticker/");

And got the error

Code:

XMLHttpRequest cannot load https://www.bitstamp.net/api/ticker/. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://rgbkey.github.io' is therefore not allowed access.

I would appreciate if anyone could tell me why this doesn't work. I can load the page fine from my web browser.

[9inety7even]

Like the error says, you're trying to make a cross-domain request, which it looks like bitstamp doesn't allow. You have a few options here, but I think the best one would just be to proxy the request through your servers. You can find some more info and code for doing that in PHP at these links:

http://stackoverflow.com/questions/19821753/jquery-xml-error-no-access-control-allow-origin-header-is-present-on-the-req
http://stackoverflow.com/questions/12683530/origin-http-localhost-is-not-allowed-by-access-control-allow-origin

[gogodr]

I use a work around for your problem here:
http://btca.frikicorp.com/
I use whateverorigin, it bypasses the cross domain control with a clever trick (setting up a local proxy)
I use the btc-e api here, but you can get the idea

$.getJSON('http://whateverorigin.org/get?url=https://btc-e.com/api/2/btc_usd/ticker&callback=?', function(data){
       BTCBuy = JSON.parse(data.contents).ticker.buy;
       BTCSell = JSON.parse(data.contents).ticker.sell;
      });

[olsn]

I'd go with gogodr's solution, it'll be the simplest for you - BUT ONLY IF you just request public ticker data, you should in NO CASE send private user-data (passwords ect...) through 3rd-party proxy-services.
If you want to read more about JSONP and how to evade the cross-domain issue for JSON-requests, you can take a look here: http://en.wikipedia.org/wiki/JSONP (or google for JSONP)

[RGBKey]

I'd go with gogodr's solution, it'll be the simplest for you - BUT ONLY IF you just request public ticker data, you should in NO CASE send private user-data (passwords ect...) through 3rd-party proxy-services.
If you want to read more about JSONP and how to evade the cross-domain issue for JSON-requests, you can take a look here: http://en.wikipedia.org/wiki/JSONP (or google for JSONP)

Thanks to gogodr, that should work just fine, and of course I'll only be using it for non-private information.

[Zickafa]

If you whant to make a site that would display API data from multiple exchanges and display it to the user use php better!

[9inety7even]

I'd go with gogodr's solution, it'll be the simplest for you - BUT ONLY IF you just request public ticker data, you should in NO CASE send private user-data (passwords ect...) through 3rd-party proxy-services.
If you want to read more about JSONP and how to evade the cross-domain issue for JSON-requests, you can take a look here: http://en.wikipedia.org/wiki/JSONP (or google for JSONP)

Thanks to gogodr, that should work just fine, and of course I'll only be using it for non-private information.

The only other thing to be careful of is that you're now putting yourself in the hands of whateverorigin: they could send back false or even malicious data. Not that I have any reason to suspect that they would, but it's just something to think about.

If you whant to make a site that would display API data from multiple exchanges and display it to the user use php better!

He could still be using PHP; he just wants the client to load the information instead of doing it on the server.

[gogodr]

I'd go with gogodr's solution, it'll be the simplest for you - BUT ONLY IF you just request public ticker data, you should in NO CASE send private user-data (passwords ect...) through 3rd-party proxy-services.
If you want to read more about JSONP and how to evade the cross-domain issue for JSON-requests, you can take a look here: http://en.wikipedia.org/wiki/JSONP (or google for JSONP)

Thanks to gogodr, that should work just fine, and of course I'll only be using it for non-private information.

The only other thing to be careful of is that you're now putting yourself in the hands of whateverorigin: they could send back false or even malicious data. Not that I have any reason to suspect that they would, but it's just something to think about.

If you whant to make a site that would display API data from multiple exchanges and display it to the user use php better!

He could still be using PHP; he just wants the client to load the information instead of doing it on the server.

if that ever were to happen, they have their whole project open sourced. Anyone can take the source and make his own whateverorigin.
There are a couple of limitations though. you cant POST or GET parameters using whateverorigin.

[RGBKey]

I'd go with gogodr's solution, it'll be the simplest for you - BUT ONLY IF you just request public ticker data, you should in NO CASE send private user-data (passwords ect...) through 3rd-party proxy-services.
If you want to read more about JSONP and how to evade the cross-domain issue for JSON-requests, you can take a look here: http://en.wikipedia.org/wiki/JSONP (or google for JSONP)

Thanks to gogodr, that should work just fine, and of course I'll only be using it for non-private information.

The only other thing to be careful of is that you're now putting yourself in the hands of whateverorigin: they could send back false or even malicious data. Not that I have any reason to suspect that they would, but it's just something to think about.

If you whant to make a site that would display API data from multiple exchanges and display it to the user use php better!

He could still be using PHP; he just wants the client to load the information instead of doing it on the server.

I really want to do as much as I can in javascript and will only resort to PHP as a last resort. Also, a MITM is no problem because all i'm fetching is ticker data. They can't really do anything with that and nothing important is going to be stored on the site anyways.