atom feed12 messages in org.apache.tomcat.usersRe: Cache-Control headers not being a...
FromSent OnAttachments
Zampani, MichaelAug 16, 2011 1:42 pm 
Christopher SchultzAug 16, 2011 1:57 pm 
Richard FrovarpAug 16, 2011 2:01 pm 
Zampani, MichaelAug 16, 2011 2:20 pm 
Mark ThomasAug 17, 2011 12:33 am 
Zampani, MichaelAug 22, 2011 2:38 pm 
Christopher SchultzAug 23, 2011 6:47 am 
Zampani, MichaelAug 23, 2011 11:08 am 
Christopher SchultzAug 23, 2011 12:10 pm 
Mark ThomasAug 23, 2011 12:48 pm 
Zampani, MichaelAug 23, 2011 1:39 pm 
Mark ThomasAug 23, 2011 1:43 pm 
Subject:Re: Cache-Control headers not being added to secure requests
From:Richard Frovarp (rfro@apache.org)
Date:Aug 16, 2011 2:01:54 pm
List:org.apache.tomcat.users

On 08/16/2011 03:57 PM, Christopher Schultz wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Michael,

On 8/16/2011 4:42 PM, Zampani, Michael wrote:

I don't understand why it was ever present, though. Does anybody know why you wouldn't want these headers on secure requests?

The svn comment says "...to reduce the likelihood of issues when downloading files with IE.". Presumably, [MS]IE has "issues" with downloading files with those response headers.

Some versions of MSIE have problems downloading files depending on the cache-control header. We've seen this with our course management system. From what I've seen IE doesn't download files, it caches them, then copies them into place on the filesystem. But due to the cache control headers, it couldn't copy the cached file because it wasn't allowed to, causing trouble.