Agent 4 flags invalid resource for any resource that contains an asterisk and a 403 is returned.
This breaks existing resource resolution for a customer who is migrating from agent 3.x and uses ElasticSearch. This change seems to be hard coded and not affected by com.forgerock.agents.agent.invalid.url.regex.
mkdir <apache dir>/htdocs/*
touch <apache dir>/htdocs/*/index.html
try to access url/*/index.html
This will be seen in the agent log:
2016-01-11 08:28:23.840 +0000 WARNING [0x7f649a5f6700:4429] policy_compare_url(): invalid resource 'https://mysub.mydomain.com:443/*/index.html'