immutable cache and auto everything

Comments

4 comments

  • Avatar
    worldswingdeejays

    Hi, 

    It seems the flag does not work.. I can't see a modification in the cache header. Can you confirm ?

     

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Ido

    Hi

    "fl_immutable_cache" is currently only supported for FF. "f_auto" mainly converts to "webp" and "jpeg-xr" formats, which are not supported by FF. So in case of using both "fl_immutable_cache" and "f_auto" with FF would decide on jpg vs png. In case the resource was already cached in the browser, it would return it without a new request.

    Regarding the responsive images - each version of the responsive image has different dimensions and its own URL, the browser caching only applies on the level of the URLs so they will be treated separately
    meaning that for every image with different dimensions, a request will go to the server, and then if an immutable header is returned the browser would not ask for that particular URL again but use the cache.

    With that being said, we noticed that the header is indeed not returned correctly in a specific use case, and there is an open request with our dev team to look into this.

    We will update the thread as soon as there are any new insights regarding this.

    0
    Comment actions Permalink
  • Avatar
    worldswingdeejays

    Hi,

     

    Any news or workaround ?

     

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Ido

    Hi

     

    Our team is in the process of reviewing this and determining the best approach to handle the edge case.

    We aim to start work on this in mid December.

    As soon as there are any insights, we will update the thread.

     

    Thanks.

    0
    Comment actions Permalink

Please sign in to leave a comment.