Apache returns 500 code instead of 404 code when a context that does not exist is accessed by using mod_cluster
Issue
- If a wrong application name is accessed through Apache httpd, the response is 500 code, but it should be a 404 code. The requests are proxied to
mod_cluster
as following:
ProxyPass / balancer://mycluster stickysession=JSESSIONID|jsessionid nofailover=On
ProxyPassReverse / balancer://mycluster
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 6.x
- Red Hat JBoss Web Server (EWS) 2.0.1
- mod_cluster 1.2.4 Final
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.