Hi all, is it possible to filter 404 application errors taking into account content-type beside http return code in jk configuration. I need to difference between application is not deployed/executing (http 404 content-type html) and application running and returning a 404 json response (content-type json)
I have put mod-jk in debug mode and content-type is showed in logs. I have not seen in documentation if a fail_on_status can be combined with content-type returned. right now my worker.properties worker.list=clusterapp # template worker.template.port=8009 worker.template.type=ajp13 # En fail-over cuenta 1 prepost + 2 (intentos) connect worker.template.prepost_timeout=10000 worker.template.connect_timeout=5000 worker.template.reply_timeout=20000 worker.template.socket_connect_timeout=10000 worker.template.connection_pool_timeout=600 # El interface REST devuelve 404 en el resto el 404 es error worker.template.fail_on_status=503 # ------------------------ # First tomcat server # ------------------------ worker.node1.reference=worker.template worker.node1.host=tomcat01.fqdn # ------------------------ # Second tomcat server # ------------------------ worker.node2.reference=worker.template worker.node2.host=tomcat02.fqdn # ------------------------ # Load Balancer worker # ------------------------ # Worker para el cluster jboss de produccion worker.clusterapp.type=lb worker.clusterapp.balanced_workers=node1,node2 worker.clusterapp.sticky_session=true my uriwrokermap.properties file is: # rest not fail over with 404 /app/rest/*=clusterapp /app/*=clusterapp;fail_on_status=404 Thanks in advance for any help. -- Saludos.
