[JBoss JIRA] (MODCLUSTER-352) Default Port Change
by Fernando Ribeiro (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-352?page=com.atlassian.jira.pl... ]
Fernando Ribeiro updated MODCLUSTER-352:
----------------------------------------
Description:
When deploying in many enterprise customers, I have found that the default port is blocked by several security products because it was used by IRC and Napster.
The default port should be changed to avoid these issues.
was:
When deploying mod_cluster in enterprise customers, I found that the default port is blocked by several security products because it was used by IRC and Napster.
The default port should be changed to avoid these issues.
> Default Port Change
> -------------------
>
> Key: MODCLUSTER-352
> URL: https://issues.jboss.org/browse/MODCLUSTER-352
> Project: mod_cluster
> Issue Type: Enhancement
> Affects Versions: 1.2.4.Final
> Environment: All supported environments.
> Reporter: Fernando Ribeiro
> Assignee: Jean-Frederic Clere
>
> When deploying in many enterprise customers, I have found that the default port is blocked by several security products because it was used by IRC and Napster.
> The default port should be changed to avoid these issues.
--
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, 4 months
[JBoss JIRA] (MODCLUSTER-352) Default Port Change
by Fernando Ribeiro (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-352?page=com.atlassian.jira.pl... ]
Fernando Ribeiro updated MODCLUSTER-352:
----------------------------------------
Description:
When deploying mod_cluster in enterprise customers, I found that the default port is blocked by several security products because it was used by IRC and Napster.
The default port should be changed to avoid these issues.
was:
When deploying mod_cluster in enterprise customers, I found that port 6666 is blocked by several AV/firewall products because it was used by IRC and Napster.
The default should be changed to a different port to prevent these issues.
> Default Port Change
> -------------------
>
> Key: MODCLUSTER-352
> URL: https://issues.jboss.org/browse/MODCLUSTER-352
> Project: mod_cluster
> Issue Type: Enhancement
> Affects Versions: 1.2.4.Final
> Environment: All supported environments.
> Reporter: Fernando Ribeiro
> Assignee: Jean-Frederic Clere
>
> When deploying mod_cluster in enterprise customers, I found that the default port is blocked by several security products because it was used by IRC and Napster.
> The default port should be changed to avoid these issues.
--
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, 4 months
[JBoss JIRA] (MODCLUSTER-352) Default Port Change
by Fernando Ribeiro (JIRA)
Fernando Ribeiro created MODCLUSTER-352:
-------------------------------------------
Summary: Default Port Change
Key: MODCLUSTER-352
URL: https://issues.jboss.org/browse/MODCLUSTER-352
Project: mod_cluster
Issue Type: Enhancement
Affects Versions: 1.2.4.Final
Environment: All supported environments.
Reporter: Fernando Ribeiro
Assignee: Jean-Frederic Clere
When deploying mod_cluster in enterprise customers, I found that port 6666 is blocked by several AV/firewall products because it was used by IRC and Napster.
The default should be changed to a different port to prevent these issues.
--
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, 4 months
[JBoss JIRA] (MODCLUSTER-351) 500 error when using ProxyPassReverse and proxying RewriteRule to the balancer
by Aaron Ogburn (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-351?page=com.atlassian.jira.pl... ]
Aaron Ogburn updated MODCLUSTER-351:
------------------------------------
> 500 error when using ProxyPassReverse and proxying RewriteRule to the balancer
> ------------------------------------------------------------------------------
>
> Key: MODCLUSTER-351
> URL: https://issues.jboss.org/browse/MODCLUSTER-351
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04, 1.2.4.Final
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Priority: Minor
>
> Looks like some compatability issues exist between Rewrites to the mod_cluster balancer and a ProxyPassReverse for it.
> <VirtualHost *:80>
> RewriteEngine On
> RewriteRule ^/foo/(.*)$ balancer://mycluster/foo/$1 [P,L]
> ProxyPassReverse /foo/ balancer://mycluster/foo/
> </VirtualHost>
> Requests served through the above VHost config fail with a 500. The log shows:
> [Thu Aug 08 16:38:50 2013] [debug] mod_proxy_cluster.c(3448): proxy: CLUSTER no balancer for balancer://mycluster/foo/hi.jsp
> [Thu Aug 08 16:38:50 2013] [debug] proxy_util.c(1525): [client 127.0.0.1] proxy: *: found reverse proxy worker for balancer://mycluster/foo/hi.jsp
> [Thu Aug 08 16:38:50 2013] [debug] mod_proxy.c(1015): Running scheme balancer handler (attempt 0)
> [Thu Aug 08 16:38:50 2013] [debug] mod_proxy_http.c(1955): proxy: HTTP: declining URL balancer://mycluster/foo/hi.jsp
> [Thu Aug 08 16:38:50 2013] [debug] mod_proxy_ajp.c(664): proxy: AJP: declining URL balancer://mycluster/foo/hi.jsp
> [Thu Aug 08 16:38:50 2013] [warn] proxy: No protocol handler was valid for the URL /foo/hi.jsp. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
> Removing the ProxyPassReverse, the request works again. Looks like the balancer isn't found for some reason with both the Rewrite and ProxyPassReverse.
--
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, 4 months
[JBoss JIRA] (MODCLUSTER-351) 500 error when using ProxyPassReverse and proxying RewriteRule to the balancer
by Aaron Ogburn (JIRA)
Aaron Ogburn created MODCLUSTER-351:
---------------------------------------
Summary: 500 error when using ProxyPassReverse and proxying RewriteRule to the balancer
Key: MODCLUSTER-351
URL: https://issues.jboss.org/browse/MODCLUSTER-351
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.2.4.Final, MOD_CLUSTER_1_0_10_GA_CP04
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
Priority: Minor
Looks like some compatability issues exist between Rewrites to the mod_cluster balancer and a ProxyPassReverse for it.
<VirtualHost *:80>
RewriteEngine On
RewriteRule ^/foo/(.*)$ balancer://mycluster/foo/$1 [P,L]
ProxyPassReverse /foo/ balancer://mycluster/foo/
</VirtualHost>
Requests served through the above VHost config fail with a 500. The log shows:
[Thu Aug 08 16:38:50 2013] [debug] mod_proxy_cluster.c(3448): proxy: CLUSTER no balancer for balancer://mycluster/foo/hi.jsp
[Thu Aug 08 16:38:50 2013] [debug] proxy_util.c(1525): [client 127.0.0.1] proxy: *: found reverse proxy worker for balancer://mycluster/foo/hi.jsp
[Thu Aug 08 16:38:50 2013] [debug] mod_proxy.c(1015): Running scheme balancer handler (attempt 0)
[Thu Aug 08 16:38:50 2013] [debug] mod_proxy_http.c(1955): proxy: HTTP: declining URL balancer://mycluster/foo/hi.jsp
[Thu Aug 08 16:38:50 2013] [debug] mod_proxy_ajp.c(664): proxy: AJP: declining URL balancer://mycluster/foo/hi.jsp
[Thu Aug 08 16:38:50 2013] [warn] proxy: No protocol handler was valid for the URL /foo/hi.jsp. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Removing the ProxyPassReverse, the request works again. Looks like the balancer isn't found for some reason with both the Rewrite and ProxyPassReverse.
--
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, 4 months