Different caching policies

As Dawn said in v10 you need to create custom leaf nodes in the WA policy.

 

using your example,

 

- Www.host.com/kkkk/ * -> send to politics 1

 

- Www.host.com/abcd/ * -> send to politics 2

 

What do you want to do with these requests? the matching criteria in the WA policy will use mime type and extension to match an existing leaf node in the WA policy. Once you know what policy your matching now you can create another leaf node but add the path for the URI example to add a new leaf node for js and css objects click on the components branch node and then click on Add to add a new leaf node, give it a name and click on create and the new leaf will be added. If you want it to match the css and js objects for your uri /kkkk/ click on the new leaf node, then click on path on the right side. Then in the value(s) box enter /kkkk/. Now you have a leaf node that only matches /kkkk/ next you need to add a parameter. next to the Add button to add parameter click on the arrow to Add a parameter and select content type then click on Add. to match the css and js objects type in includes in the box to the right if Value matches, click the check box to the left of value matches and click on Save. Now you have a leaf node that only matches objects that start with /kkkk/ and have a extension or mime type that matches whats in the includes object type. now you can customize this leaf node by selecting the Acceleration rules menu and there you set Assembly rules and life time rules based on your needs.. I also move the new leaf node up in the branch so it’s above the original includes leaf node so it matches before the includes (just in case there is an order of operations)

 

that’s how we handle custom caching for specific URIs.