… the underlying connect.static.send which defaults to maxAge=0 (i.e. they are immediately stale). This has the undesirable consequence that any image files served by gZippo are thus never cached by the browser (the browser does reuse the file, but it always queries the server with an If-Modified-Since). With this change, we use gZippo's maxAge value when 'pass'ing to connect. This brings up an interesting issue of whether gZippo is intended solely for gzippable content ... or whether it should try to replicate normal 'static' middleware behavior for other content types (e.g. images). It might be interesting to contemplate using the same 'options' format for gZippo as the underlying connect middleware for maximum overlap.
… is not in path
…stantiate a new date object
…backwards (>= instead of <= as it should have been) and that's why the test was failing. I'm converted to TDD.
…eady tested this in the 'real world' with Express and Firefox.
…hattiness' with the console.log code accidentally left in.
…s headers so client-side caching works on gzipped files. 2) Add 304 HTTP Header response if client requests confirmation that current cached version is most up-to-date.