[richfaces-issues] [JBoss JIRA] Resolved: (RF-6258) a4j:push does't work through Apache/proxy_ajp

[Nick Belaevski (JIRA)]

     [ https://jira.jboss.org/jira/browse/RF-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Belaevski resolved RF-6258.
--------------------------------

    Resolution: Rejected
      Assignee: Tsikhon Kuprevich


Looks like a specific Apache issue.

> a4j:push does't work through Apache/proxy_ajp
> ---------------------------------------------
>
>                 Key: RF-6258
>                 URL: https://jira.jboss.org/jira/browse/RF-6258
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>         Environment: Java 1.5, JBoss 4.2.3.GA, Seam 2.1.1.GA, Apache 2.2 with mod_proxy_ajp
>            Reporter: Bob Shanahan
>            Assignee: Tsikhon Kuprevich
>
> a4j:push component works fine on various servers via port 8080. When running through Apache and mod_proxy_ajp it no longer works. Based on app logs, it appears the Seam conversation context is lost when the push component rerenders client elements.
> proxy_ajp.conf:
> ProxyPass /myapp ajp://localhost:8009/myapp
> ProxyPassReverse /myapp [***]ajp://localhost:8009/myapp

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira