mod_cluster balancer on JBCS httpd 2.4.57 now returns 404 instead of 503 if no matching enabled context

Solution Verified - Updated -

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
  • JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content