Lesti_Fpc and Miss Uri Params

I have released Lesti_Fpc 1.1.5. What is new in this version? I have add a new field in the configurations. Miss Uri Params, not a really creative and good name. The idea behind this parameters is: No request with these parameters will be cached. For example:


It’s getting a little bit complicated. All Miss Uri Param will be seperated by comma and every parameter is sperated with an = from a regular expression. Every request with the parameter limit as an integer will miss the Fpc. I know it makes the configurations complexer, but I guess it will help somebody.

What does that has to do with Session Params?

The reason why Lesti_Fpc didn’t answer at the beginning of magento call is the session. I need the session to make a differents between a category shown with 9 products or a category shown with 15 products. Many people think the limit is always in the uri of an category, but it’s just in the moment when a user wants to change the limit. Magento saves this parameter in the session. And if you change to an other category magento knows how much products you want see from the other category. That’s why we have Session params in the configurations. If you delete them, the category will be shown allways with 9 products in default. That’s the behavior of the most full page caches.

What was the problem with the Session params?

But I have detected an other problem with Session parameters. If the Fpc sends the response, magento can’t change for example limit in the session. And so I did have the problem as before. That’s why I want to miss every request with limit as an integer.

You think you didn’t need that?

If you think you didn’t need that behavior and want more hits and less misses, you should delete the Session Params and Miss Uri Params

Future of Fpc?

I know that is a lot of configuration for such a small extension and I also didn’t like so much fields. I guess I will change this in in version 2 completly and will stop using fields seperated with comma.

13 thoughts on “Lesti_Fpc and Miss Uri Params”

  1. Hello Gordon,

    We have a strange problem with Manadev Layered Navigation and Lesti FPC 1.1.5. With Ajax enabled and Remember Applied Category Filters set to Yes, some categories have already predefined filters activated without reasons ?

    We have downgraded to Lesti FPC 1.1.4, and it works better.

    Have you a clue ?


  2. Re,

    It is already done, like I said when we downgrade, we have no problem.
    It appears only with the new version 1.1.5

    I have no clue where it can comes from.
    We have contacted the author of the extension directly.

  3. Hello Lesti,

    we have some issues with layered navigation.
    As we change products pretty often, we don’t want those pages to be cached (as usually when customer goes to this page, Lesti FPC tries to cache it and it takes really lot of time).

    Pages, like:

    They are loading more than 10 seconds, when Lesti FPC is turned on.
    But when FPC is turned off, than everything goes ok, and load time is about 2-3 seconds.

    I have tried to add to Miss URI params:

    To prevent those pages from caching, to save time. But it didn’t work.

    Please, help.

        1. Gordon, can you, please, tell me.

          When we added miss uri to settings – how does extension process those pages? Can it just ignore them (not to spend time on processing)?

    1. Hello Gordon,

      where you able to check the issue with long loading of the pages, that should not be cached?

  4. I’m using the FME One Step Checkout module; we have a high rate of people falling off the page, refreshing it and leaving. I suspect that because it is not a standard url, that it is being cached.

    How would I exclude a url from my website from the cache, which section would I put it in?

    Thank you


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>