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

    a4j:push with apache mod_proxy

    Chris Dollar Novice

      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