mod_cluster-issues April 2013

mod_cluster-issues@lists.jboss.org

1 participants
14 discussions

[JBoss JIRA] (MODCLUSTER-328) mod_cluster doesn't recognize ? as a proper context delimiter causing 503s on requests with query strings

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-328?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-328: ------------------------------------ Fix Version/s: 1.2.4.Final (was: 1.2.3.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 > Fix For: 1.2.4.Final > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-328) mod_cluster doesn't recognize ? as a proper context delimiter causing 503s on requests with query strings

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-328?page=com.atlassian.jira.pl... ] Ingo Weiss commented on MODCLUSTER-328: --------------------------------------- EWS 2.0 comes with mod_cluster 1.2.3.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 > Fix For: 1.2.3.Final > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-328) mod_cluster doesn't recognize ? as a proper context delimiter causing 503s on requests with query strings

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-328?page=com.atlassian.jira.pl... ] Ingo Weiss updated MODCLUSTER-328: ---------------------------------- Fix Version/s: 1.2.3.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 > Fix For: 1.2.3.Final > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-333) STOP-APP not included on mod_cluster-manager page along with ENABLE/DISABLE-APP

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-333: --------------------------------------- Summary: STOP-APP not included on mod_cluster-manager page along with ENABLE/DISABLE-APP Key: MODCLUSTER-333 URL: https://issues.jboss.org/browse/MODCLUSTER-333 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.3.Final Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere Priority: Minor Links for the STOP-APP command are not exposed on the mod_cluster-manager page although ENABLE-APP and DISABLE-APP are. Can STOP-APP be added to the mod_cluster-manager page? The STOP-APP request to this page can be manually crafted and it works so it looks like the functionality is there; it'd just need the link generated representing that command. -- 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

11 years

1
0
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2013