Strange HTTPS/Cache Behavior

[paul at gtcomm.net]

1) Caching depending on mime-types
Server has includes https caching instructions to cache
jpg/gif/js/css files for 1 hour
however these parameters seem removed from the headers. 
How can this be passed browsers - we need this data to be cached.

2) In HTTPS side there are several js/css includes that are BLOCKED for
loading
It works ok on HTTP, but seems to be blocked with HTTPS. It works 1 of 10
times, but most of the time, no include files are loaded.
A temporary fix was to make all css and js to be included inside html
document, 
but this is not very good idea.  Is there a way to fix this?


Thanks

Paul