Cache and prioritize_critical_css filter reuse

[Kevin]

Hello,

I'm currently experimenting with this library, and was wondering if a certain funcionality is possible. For example, let's say I have a dynamic website, with pages generated on the fly with a structured URL like https://example.com/post/[some-dynamic-slug]. With this in place, as of my understanding, the prioritize_critical_css filter needs to access each auto generated page a couple of times until it does it's magic. But, given the nature of the structured dynamic content and static assets (yes, it's not a general use case, but bare with me), the Critical CSS will be pratically the same for each page generated at /post/[some-dynamic-slug]. The question is, is there a way to instruct mod-pagespeed to reuse it's previously calculated prioritize_critical_css given a pattern? I looked up the docs, but couldn't find anything like this.

Thanks,

Kevin

[Joshua Marantz]

I'm vaguely remembering discussion around an option to drop query-params from property-cache keys, but can't remember whether that feature got built. And I can't find it in the docs.

In that case if your structured URL was https://example.com/post?slug=some-dynamic-slug you'd be good to go.

I could also see some sort of suffix-drop configuration that would allow your exact URL pattern to work, but I don't think that exists.

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/fe992413-4882-45f3-a558-79f448f7b52bn%40googlegroups.com.