UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36

Steps to reproduce the problem:
1. Run the following script in node locally (using: npm install express && node script.js):

var express = require('express');
var app = express();
app.get('/nocache', function(req, res) {
    res.setHeader('Cache-Control', 'private, max-age=0, no-cache');
    res.send(new Date().toString() + '<br><a href="https://mixmax.com">Click to navigate away and then press ' +
        'Back. It will show the same timestamp.</a>');
});
app.get('/nostore', function(req, res) {
    res.setHeader('Cache-Control', 'no-cache, no-store');
    res.send(new Date().toString() + '<br><a href="https://mixmax.com">Click to navigate away and then press ' +
        'Back. It will update the timestamp.</a>');
});
app.listen('8030');

2. Visit http://localhost:8030/nocache. Click the link, then click the back button. Notice the timestamp isn't updated.
3. Now visit http://localhost:8030/nocache. Click the link, then click the back button. Notice the time IS updated.

What is the expected behavior?
See above

What went wrong?
In step 2, I'd expect Chrome to serve up a fresh copy of the content since the no-cache header is present. However, I apparently also need to add the 'no-store' header.

WebStore page: 

Did this work before? N/A 

Chrome version: 44.0.2403.125  Channel: n/a
OS Version: OS X 10.10.4
Flash Version: Shockwave Flash 18.0 r0