We are still running Access Manager 4.1.2 and encounter an issue with Global Advanced Options : noURLNormalize=on running together on the same cluster with a protected resource that requires : allowEncodedSlashes=nodecode.
When we enable the noURLNormalize=on, the protected resource using the allowEncodedSlashes will fail.
In Access Manager 4.1, the allowEncodedSlashes was not yet introduced as a Global Advanced option. From version 4.2 and higher it is a Global Advanced option. For this reason, we had to force the allowEncodedSlashes advanced setting on the protected resources and in the Apache startup config.

Has anyone encountered this behaviour? If so, is there a solution to run both options on the same Access Gateway cluster?

kind Regards,

Michel Hulsen