MtGox API may return cached data on HTTPS

[Jan]

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.

[1715582721]

1715582721

[1715582721]

1715582721

[phatsphere]

that's crap

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]

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.

[frito]

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]

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.

[frito]

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!