News for hackers. Stuff that matters.
Re:HTTP GZIP Compression remote date and time leak by raverbashing on Monday February 22, 2016 @06:07AM (#11149997)
The concerns are valid but it is ironic that's being served from an http only page.

(Why does GZIP needs a compression date again?)

Re:HTTP GZIP Compression remote date and time leak by filmor on Monday February 22, 2016 @06:40AM (#11150126)
AFAIK it's not the compression date but instead the last modified date stored in the filesystem metadata. It's likely there such that `gzip file; gunzip file.gz` keeps the mtime information intact.
Re:HTTP GZIP Compression remote date and time leak by masklinn on Monday February 22, 2016 @06:46AM (#11150156)
The problem's it's any date so which date is stored depends on the library and the datasource. If you're gzipping and caching dynamic content there's no filesystem mtime, so you'll probably get the compression time instead (unless the remote end or library defaults to 0)