]
RH Bugzilla Integration commented on MODCLUSTER-335:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> made a comment on [bug
Regression in ProxyPass integration
-----------------------------------
Key: MODCLUSTER-335
URL:
https://issues.jboss.org/browse/MODCLUSTER-335
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.2.4.Final
Environment: RHEL6 x86_64, the rest is to be confirmed...
Reporter: Michal Babacek
Assignee: Jean-Frederic Clere
Fix For: 1.2.5.Final
Attachments: logs-and-configs-m_c-1.2.3.zip, logs-and-configs-m_c-1.2.4.zip,
test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log,
test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
This configuration & test worked just fine with 1.2.3.Final and it is broken in
1.2.4.Final, so we have a *regression* here, I guess.
{code}
ProxyPassMatch ^/app/static/ !
ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
ProxyPass / !
ProxyPassReverse /app balancer://qacluster
ProxyPassReverseCookieDomain / /app/
ProxyPassReverseCookiePath / /app/
ProxyPreserveHost on
{code}
Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes
from the famous
[
CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
h3. mod_cluster 1.2.3 ProxyPass test:
*Failed tests*
* modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must
always be the same.
* modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334],
http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
h3. mod_cluster 1.2.4 ProxyPass test:
*Failed tests*
* modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail,
http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
* modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334],
http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
What the test does is it accesses various URLs, getting either static content from httpd
or a dynamic one from application server.
Browse the attached files for complete configs, debug logs and test results. Ping me, if
the zipped file structure does not make sense to you...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: