It looks like safari simply ignores a 304 response and renders a blank body... I'm guessing that dnc253 and tasseKATT were right, in that the debug tools just disabled cache.
For some reason adding a fake meta header like <meta name="304Fix" content="safari-fix">
fixed the problem ... I have 0 understanding of why.