3 Replies Latest reply on Jun 16, 2008 6:26 PM by cdollar393

    a4j:push with apache mod_proxy

    cdollar393

      Hi All,

      I'm working on getting my app ready for production so I've spent some time getting mod_proxy working with apache per the instrctions here http://wiki.jboss.org/wiki/UsingMod_proxyWithJBoss (I'm using AJP as well), and now I have that working so my app can be accessed at port 80 via mod_proxy + apache or via 8080 going directly to jboss + tomcat.

      The one issue I'm seeing is that when the page is accessed via port 80 my a4j:push doesn't work. If I access it via port 8080 it works fine. I started examining the conversation with firebug and noticed that when the push fires a HEAD request is sent. Taking a look at that HEAD request a bit more I noticed that the response headers for the port 80 requests weren't the same as they were for 8080.

      Here's what firebug got for port 80:
      http://imagebin.ca/view/clTang.html

      And here's 8080:
      http://imagebin.ca/view/wqPIwbp.html

      And I also see in the 8080 requests that I get a 'Ajax-Push-Status READY' header when the push 'fires'.

      Does anyone have any ideas what the problem might be?

      Thanks!
      Chris

        • 1. Re: a4j:push with apache mod_proxy
          cdollar393

          I should add that I'm using 3.2.1.GA and with my mod_proxy configuration I'm not using any load balancing - its just 1 single server running both jboss and apache.

          Thanks for the help.

          Chris

          • 2. Re: a4j:push with apache mod_proxy
            cdollar393

            Any ideas? Does anyone have a push working with mod_proxy or know of any reason why this shouldn't work?

            Thanks again.
            Chris

            • 3. Re: a4j:push with apache mod_proxy
              cdollar393

              SOLVED! The problem was with the mod_proxy_ajp module with my version of apache. Specifically, versions of the mod_proxy_ajp module prior to the one in apache 2.2.7 forward all HEAD requests as GET requests, which messes things up for a push since it sends a HEAD request to see if it needs to do a full request.

              Upgrading to apache >2.2.7 fixed the issue for me.

              Chris