You can achieve it by the following pattern
your-domain/client/(.*)
you may check it by view source any page that contains “client” its exclude from the cache
like: your-domain/client/test
Hi Adeelkhan, Thanks for the reply.
I understand that with that pattern…
your-domain/client/(.*)
… only be excluding everything that hangs from your-domain/client/(.*)
But my intention is to exclude everything that hangs from /client/, from any domain.
As I mentioned, having a multisite environment with the domain mapping option enabled, the part of your-domain is not always the same and also I do not know it.
For that reason I was wondering if this pattern would be valid.¿?
(.*)/client/(.*)
-
This reply was modified 4 years, 8 months ago by
kikexxxito.
In multisite, Breeze gives separate settings of each subsite in a multisite environment.
you have to define separate rules for the exclusion of each site.
(.*)/client/(.*) the pattern is not valid of any multisite exclusion rules.
Hi @adeelkhan
in that case, we will have to do some automation so that when a new domain is created, it writes the caching exclusion.
To have the complete information, said cache exclusion field is saved in a field of the database? Could you tell me which one?
Can you think of a better solution to solve the problem we are having?
Any cache plugins set the rules after the domain creations Because the first domain created /configured then cache plugins applied its settings. So first create the domain then apply exclusion rules.