Apache fails to proxy saying "No protocol handler was valid for the URL"
Issue
- mod_cluster fails to proxy our traffic, returns a 500 response, and yields the following:
[warn] proxy: No protocol handler was valid for the URL /foo. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Environment
- Apache httpd
- mod_cluster
- mod_proxy_balancer
- JBoss Enterprise Application Platform (EAP)
- JBoss Enterprise Web Server (EWS)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
