Hello, in "bsd.apache.mk" SUEXEC_DOCROOT is set to "${PREFIX}/www/data". But the "htdocsdir" from apache22 is set to "${PREFIX}/www/apache22/data" (in "patch-config.layout"). Thus, in a normal build, suEXEC can't work "out of the box". Regards, Carsten Fix: a) set "datadir" from apache22 to ${PREFIX}/www" (like in apache20) or b) make a "if apache22 SUEXEC_DOCROOT=${PREFIX}/www/apache22/data" in "bsd.apache.mk". BTW: Don't you think it's better to set SUEXEC_DOCROOT to Apache's "datadir", instead to the "htdocsdir"? Because "cgi-bin" is not a subdir of the "htdocsdir", it's also a subdir of the "datadir". How-To-Repeat: install www/apache22 with suEXEC from the ports - grep "^DocumentRoot" /usr/local/etc/apache22/httpd.conf - suexec -V (look for AP_DOC_ROOT) See the different diretories.
Responsible Changed From-To: freebsd-ports-bugs->clement Over to maintainer (via the GNATS Auto Assign Tool)
> Description: > in "bsd.apache.mk" SUEXEC_DOCROOT is set to "${PREFIX}/www/data". But the > "htdocsdir" from apache22 is set to "${PREFIX}/www/apache22/data" (in > "patch-config.layout"). Thus, in a normal build, suEXEC can't work "out > of the box". > > Fix: > a) set "datadir" from apache22 to ${PREFIX}/www" (like in apache20) > or b) make a "if apache22 SUEXEC_DOCROOT=${PREFIX}/www/apache22/data" in > "bsd.apache.mk". Hello, I think, the best way is a). Because at the moment I'm installing the port "devel/websvn". And the install dir for this port/package is also "${PREFIX}/www/data/websvn". Maybe there are also some other ports, with assume that the "htdocsdir" is "${PREFIX}/www/data/" and not "${PREFIX}/www/apache22/data/". Is there any reason, why the "config.layout" from Apache is patched from the apache22 port? Regards, Carsten
Responsible Changed From-To: clement->apache apache team
Back to pool
Is this PR still relevant?