Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-1001

mod_cluster can't handle local http requests with ws

XMLWordPrintable

    • 8
    • False
    • False
    • -
    • Undefined
    • Hide

      1. Configure mod_cluster on httpd with JBoss and enable ws:

      EnableWsTunnel
      WSUpgradeHeader none
      

      2. Deploy an /app
      3. Request local content from httpd DocumentRoot and note it is served
      4. Make an http request proxied through mod_cluster for /app
      5. Request local content from httpd DocumentRoot again and now note 404 if request is on same connection as step

      Show
      1. Configure mod_cluster on httpd with JBoss and enable ws: EnableWsTunnel WSUpgradeHeader none 2. Deploy an /app 3. Request local content from httpd DocumentRoot and note it is served 4. Make an http request proxied through mod_cluster for /app 5. Request local content from httpd DocumentRoot again and now note 404 if request is on same connection as step

      mod_cluster can't handle local http requests with ws. This causes issues if content needs to be served locally from htpd for HTTP requests. Even proxing an http request, the proxy upgrades that to a ws tunnel. Then if the client makes another http request on their keepalive connection tied to that tunnel, the request is automatically sent on the ws tunnel, even if it does not match a enabled context. This means a 404 is seen from the backend instead of serving the content locally from httpd's DocumentRoot.

              gzaronik@redhat.com George Zaronikas
              rhn-support-aogburn Aaron Ogburn
              Paul Lodge Paul Lodge
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: