Chrome is a known issue where SSL and SPDY requests are not being decoded. I have a fix that I hope to implement in the next week or so (assuming things don't get too crazy).

I'm not sure why the resources look the way they do in IE but the strange part is that the headers look reasonable and some of the HTTPS resources DO have expires times on them. Do you see it consistently for the same resources? I'm wondering if maybe something funky happened with the akamai edge node that the WPT agent hit.

I don't think it's that issue but it may be similar logic of some kind (and I'm not sure that it's on Akamai's end). Looking at the responses themselves, it looks like all of the css and js are being served without cache control headers but all of the images are.