How do I prevent routing static content in IHS to Plugin?

I have a Liberty infrastructure with an IHS in front. So in between there is the plugin. I configured the plugin to route any request on /* to my app server. This works quite good because I don't have to (re-)generate the plugin after deployment.

Another approach with Liberty is to use the Dynamic Routing capability in the Collective controller - you only need to generate the plugin config once, after that the controller will feed any routing updates dynamically to the Plugin - with no manual steps and no delays.

All you need for this is one server (the controller) running the collectiveContoller-1.0 and dynamicRouting-1.0 features, which requires a WAS ND license. All the other servers can use their collectiveMember-1.0 feature to join to that collective; those servers can have any WAS license including Liberty Core. Updates to application routing are then automatically provided to the Plugin in IHS or DataPower.