[15:15]<decke> looks like helma's res.cache is broken.... [15:15]<decke> http://bsdpaste.bsdgroup.de/1103 [15:16]<decke> shouldn't res.cache = true; send caching header? not just Etag [15:26]<zumbrunn> decke: don't know, but to me it makes more sense if helma would add a special header when res.cache is set to false [15:26]<zumbrunn> (and maybe does nothing special when it is set to true) [15:26]<decke> i can't see much difference in both cases... [15:26]<decke> so i expected res.cache = true to send Cache-control headers [15:27]<zumbrunn> nothing gets added when it is set to false? [15:27]<decke> one moment i'll try it again to be sure... [15:31]<decke> with res.cache = false it does send: Cache-Control: no-cache, no-store, must-revalidate, max-age=0 [15:31]<decke> so that's correct [15:32]<decke> but res.cache = true; is a noop [15:32]<zumbrunn> well, res.cache = true just suppresses that [15:33]<decke> yeah it's really hard to maintain 3 cases with a boolean...