[
https://issues.jboss.org/browse/MODCLUSTER-328?page=com.atlassian.jira.pl...
]
Aaron Ogburn updated MODCLUSTER-328:
------------------------------------
Environment:
-Enterprise Application Platform (EAP) 6.0.0
-mod_cluster 1.2.1.FINAL
and
-Enterprise Application Platform (EAP) 5.1.2
-mod_cluster 1.0.10.GA_CP02
was:
-Enterprise Application Platform (EAP) 6
-mod_cluster 1.2.1.FINAL
mod_cluster doesn't recognize ? as a proper context delimiter
causing 503s on requests with query strings
---------------------------------------------------------------------------------------------------------
Key: MODCLUSTER-328
URL:
https://issues.jboss.org/browse/MODCLUSTER-328
Project: mod_cluster
Issue Type: Bug
Affects Versions: MOD_CLUSTER_1_0_10_GA_CP02, 1.2.1.Final
Environment: -Enterprise Application Platform (EAP) 6.0.0
-mod_cluster 1.2.1.FINAL
and
-Enterprise Application Platform (EAP) 5.1.2
-mod_cluster 1.0.10.GA_CP02
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
The following will all fail with 503s:
http://localhost/helloworld?test=foo
http://localhost/helloworld?test
http://localhost/helloworld?
And I noted the following all work:
http://localhost/helloworld/?test=foo
http://localhost/helloworld/?test
http://localhost/helloworld/?
So it looks like the issue here is that mod_cluster does not recognize ? as a delimiter
when checking the request context. Thus with no trailing slash it treats the query string
as part of the request context and tries to check the balancer for a deployed context of
/helloworld?... which doesn't exist and 503s. Adding the trailing slash, mod_cluster
can properly delimit this and then sees the context just as /helloworld, which can be
found on the balancer for appropriate proxying.
--
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:
http://www.atlassian.com/software/jira