Bitcoin Forum
October 23, 2017, 07:27:44 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: MtGox API may return cached data on HTTPS  (Read 1199 times)
Jan
Legendary
*
Offline Offline

Activity: 1043



View Profile
September 02, 2013, 02:31:49 PM
 #1

If you pull mtgox ticker data from their API you may look at old data.

It seems that when MtGox switched over to use AKAMAI for their web-fontend-cache the by accident also made akamai serve cached trade data.

The results you get by fetching: https://data.mtgox.com/api/1/BTCEUR/public/ticker
May be very different for what you get without HTTPS (http vs https): http://data.mtgox.com/api/1/BTCEUR/public/ticker

I noticed that one of my servers was using data back from August 20!
The results vary depending on which host you are using. You get various old sets depending on which DNS records your host has. On one host data.mtgos.com maps to e7476.b.akamaiedge.net while on another it maps to a23-53-216-44.deploy.static.akamaitechnologies.com, etc...

It seems that http is not cached.

Mycelium let's you hold your private keys private.
1508786864
Hero Member
*
Offline Offline

Posts: 1508786864

View Profile Personal Message (Offline)

Ignore
1508786864
Reply with quote  #2

1508786864
Report to moderator
1508786864
Hero Member
*
Offline Offline

Posts: 1508786864

View Profile Personal Message (Offline)

Ignore
1508786864
Reply with quote  #2

1508786864
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
phatsphere
Hero Member
*****
Offline Offline

Activity: 765


View Profile
September 02, 2013, 03:20:45 PM
 #2

that's crap Sad

is this "now" json field a timestamp? it seems to be, but there is no decimal point! divide it by 1e6 and add a sanity check on the server side to capture this, in case it happens again.

… and back to work everybody :p
caffeinewriter
Hero Member
*****
Offline Offline

Activity: 518


Eyyyy, Bitcoin Forum


View Profile WWW
September 03, 2013, 08:24:58 AM
 #3

Wow. This is absolutely nutty. This could potentially cost somebody a fair amount of money. I may have to talk to the guy at DEFCON who was selling BTC using his homemade vending machine. See which he was using. But seriously. Wow.

BTC: 13373CuvtwQGgDWYv28pm3mTxy2bGS5U4D
"You're better than Google. And almost as quick." | Bundle.FM - DRM-Free Content on your terms. COMING SOON
frito
Full Member
***
Offline Offline

Activity: 127


View Profile
November 24, 2013, 02:55:50 AM
 #4

If you pull mtgox ticker data from their API you may look at old data.

It seems that when MtGox switched over to use AKAMAI for their web-fontend-cache the by accident also made akamai serve cached trade data.

The results you get by fetching: https://data.mtgox.com/api/1/BTCEUR/public/ticker
May be very different for what you get without HTTPS (http vs https): http://data.mtgox.com/api/1/BTCEUR/public/ticker

I noticed that one of my servers was using data back from August 20!
The results vary depending on which host you are using. You get various old sets depending on which DNS records your host has. On one host data.mtgos.com maps to e7476.b.akamaiedge.net while on another it maps to a23-53-216-44.deploy.static.akamaitechnologies.com, etc...

It seems that http is not cached.
have u reported it to gox?
caffeinewriter
Hero Member
*****
Offline Offline

Activity: 518


Eyyyy, Bitcoin Forum


View Profile WWW
November 26, 2013, 09:47:07 AM
 #5

If you pull mtgox ticker data from their API you may look at old data.

It seems that when MtGox switched over to use AKAMAI for their web-fontend-cache the by accident also made akamai serve cached trade data.

The results you get by fetching: https://data.mtgox.com/api/1/BTCEUR/public/ticker
May be very different for what you get without HTTPS (http vs https): http://data.mtgox.com/api/1/BTCEUR/public/ticker

I noticed that one of my servers was using data back from August 20!
The results vary depending on which host you are using. You get various old sets depending on which DNS records your host has. On one host data.mtgos.com maps to e7476.b.akamaiedge.net while on another it maps to a23-53-216-44.deploy.static.akamaitechnologies.com, etc...

It seems that http is not cached.
have u reported it to gox?

If you check the APIs now, I'm assuming that they were as of two days ago, since this issue is relatively old now.

BTC: 13373CuvtwQGgDWYv28pm3mTxy2bGS5U4D
"You're better than Google. And almost as quick." | Bundle.FM - DRM-Free Content on your terms. COMING SOON
frito
Full Member
***
Offline Offline

Activity: 127


View Profile
December 28, 2013, 12:50:39 AM
 #6

If you pull mtgox ticker data from their API you may look at old data.

It seems that when MtGox switched over to use AKAMAI for their web-fontend-cache the by accident also made akamai serve cached trade data.

The results you get by fetching: https://data.mtgox.com/api/1/BTCEUR/public/ticker
May be very different for what you get without HTTPS (http vs https): http://data.mtgox.com/api/1/BTCEUR/public/ticker

I noticed that one of my servers was using data back from August 20!
The results vary depending on which host you are using. You get various old sets depending on which DNS records your host has. On one host data.mtgos.com maps to e7476.b.akamaiedge.net while on another it maps to a23-53-216-44.deploy.static.akamaitechnologies.com, etc...

It seems that http is not cached.

I am actually experiencing big problems with missed or greatly lagging quotes, both using websocket and REST.

When I try the http vs https REST call I can see the http being OK and https messed up!
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!