"Would it be ok to configure the "new" httpd to listen on port 8080? " Looks like a nice idea ! To this end, I edited "Listen 80" to "Listen 8080" in httpd.conf, but then I got a more laconic and surprising behavior : $ sudo bin/apachectl -k restart httpd not running, trying to start $ sudo bin/apachectl -k start httpd (pid 2823) already running But when I type http://localhost or http://localhost:8080 in my browser, I still get the 403:Forbidden If I type http://example.com:8080 in my browser (because of the line ServerName www.example.com:8080 in my httpd.conf), it gets stuck (the loading takes forever, and the browser eventually gives up with a "too long to respond" message). On Sat, Mar 19, 2016 at 12:27 PM, Luca Toscano <toscano.luca@xxxxxxxxx> wrote: > Hello! > > 2016-03-19 11:23 GMT+01:00 Roparzh Hemon <roparzhhemon@xxxxxxxxx>: >> >> >> Plus, I don't want my little experiments to >> interfere with built-in defaults on my system). >> > > Would it be ok to configure the "new" httpd to listen on port 8080? You > could keep both and this problem would disappear :) > > Luca --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|