Strange HTTPS/Cache Behavior
paul at gtcomm.net
Mon Jul 21 02:18:15 MSD 2008
Possibly.. I'll check this.. That doesn't explain the cache parameters
not being passed, and it doesn't explain why it works with http and not
jeff emminger wrote:
> could it be related to gzipping large css/js files?
> On Fri, Jul 18, 2008 at 5:43 PM, <paul at gtcomm.net> wrote:
>> Anyone have any ideas on this?
>> I'm using 0.6.32 and the mime cache data isn't being sent with the
>> responses from the proxy
>> and js/css is being blocked.
>> On Tue, 15 Jul 2008 03:47:08 -0400, <paul at gtcomm.net> wrote:
>>> 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
>>> 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
>>> but this is not very good idea. Is there a way to fix this?
More information about the nginx