3 Replies Latest reply on Oct 9, 2012 11:37 AM by Jens Marre

    Problem with standalone Apex Listener and browser image caching

    Jens Marre

      I am currently evaluating the standalone listener 1.1.4 with Oracle 11g and Apex 4.1
      Has anybody some advice or experience regarding browser image caching?

      What I am experiencing is, that the browser is sending GET-requests for every static theme content e.g. theme images, and the apex listener responds with http-ok 200. Thus, a page takes extra time to load.
      What I would expect, is that the apex listener sends reasonable "expire"-headers or at least "etag"-headers, to save the image request next time or at least to get http-not-modified 304 responses next time.

      E.g. a http response from a standalone listener for an image looks like

      HTTP/1.1 200 OK
      Content-Type: image/gif
      Content-Length: 933
      Date: Thu, 04 Oct 2012 09:46:10 GMT

      Data Size     933
      Device     disk
      Expires     Thu Jan 01 1970 01:00:00 GMT+0100
      Fetch Count     3
      Last Fetched     Thu Oct 04 2012 11:46:10 GMT+0200
      Last Modified     Thu Oct 04 2012 11:46:10 GMT+0200

      If run the listener in a Glassfish-environment, I get reasonable expire-dates and an etag.

      Thanks for any help