mod_cluster balancer on JBCS httpd 2.4.57 now returns 404 instead of 503 if no matching enabled context
Issue
- We use an explicit proxy pass to our mod_cluster balancer:
ProxyPass / balancer://mycluster/
- Previously, this always returned a 503 if the application servers were stopped and there was no matching context enabled in the balancer for the request. After upgrading to JBCS httpd 2.4.57, this now results in a 404 instead.
Environment
- JBoss Core Services (JBCS)
- Apache httpd 2.4.57
- mod_cluster
- Apache httpd 2.4.57
- JBoss Enterprise Application Platform (EAP) 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.