Simeon Pinder created MODCLUSTER-295:
Summary: default suggested port for ServerAdvertise needs to be changed to
7777 or some other unprotected port for Chrome support
Issue Type: Enhancement
Affects Versions: 1.2.0.Final
Environment: Default Httpd server provided for Linux in 1.2.0.Final release but
this would affect all platforms.
Reporter: Simeon Pinder
Assignee: Jean-Frederic Clere
If you setup mod_cluster and use the default configuration/ports used in httpd.conf of
6666 in your initial modcluster configuration, when attempting to browse http://(server
ip):6666/mod_cluster_manager from a Chrome browser you get "The webpage is not
available". Initially this feels like a 'File Not Found' exception
indicating that the mod_cluster module may not actually be setup correctly. On closer
investigation you'll see that the actual error is:
Error 312 (net::ERR_UNSAFE_PORT): Unknown error.
There's a workaround is to change the port to another port not marked as
'secured' or do what is described here but this is a hurdle to new users trying to
test out their mod_cluster integration with Chrome:
Firefox loads the same page fine.
Either way if it complicates modcluster setup and testing and we can get around it by
suggesting a different port(ex. 7777) I think this is preferable. If not we should at a
minimum include this as a note in the installation and trouble shooting guide.
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