Websocket with Http11NioProtocol connector failed with error 400 or error 500

Solution Verified - Updated -

Issue

  • Getting http 400 error and http 500 error when enabling Http11NioProtocol connector in EAP for Websocket, the httpd configuration is

    ProxyPreserveHost On      
    RewriteEngine On
    RewriteCond %{REQUEST_METHOD} ^(HEAD|GET) [NC]
    RewriteCond %{HTTP:Range} ([0-9]*-[0-9]*)(\s*,\s*[0-9]*-[0-9]*)+ [OR]
    RewriteCond %{HTTP:Request-Range} ([0-9]*-[0-9]*)(\s*,\s*[0-9]*-[0-9]*)+
    RewriteCond %{REQUEST_METHOD} ^OPTIONS
    RewriteRule .* - [F]
    RewriteCond %{HTTP:Connection} ^Upgrade$ [NC]
    RewriteCond %{HTTP:Upgrade} ^WebSocket$ [NC]
    RewriteRule /(.*) ws://10.10.10.10:8080/%{REQUEST_URI} [P]
    
    ProxyPass           /               http://10.10.10.10:8080/  keepalive=On retry=0
    ProxyPassReverse    /               http://10.10.10.10:8080/
    

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.4.18
  • Red Hat JBoss Core Services (JBCS) Apache HTTP Server
    • 2.4.23

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