Hi Eric: This may or may not be relevant, but I also have the Surgemail mail client running by proxying a port 80 address to the Surgemail socket. The point is, when I started it on Apache-2.4.25 the internal links stopped working. I had to explicitly give the entire path and everything worked again. This isn't a mod_proxy_fcgi situation, it just uses the standard mod_proxy stuff, but since mod_proxy is a required base, maybe something doesn't get passed correctly (?). Seems odd to me but I thought I had better mention it just in case. John =================================== On Sunday 14 May 2017 11:42:53 Eric Covener wrote: > On Sat, May 13, 2017 at 11:01 PM, John Iliffe <john.iliffe@xxxxxxxxx> wrote: > > Sure: > > > > ---------------------- > > # namei -m /httpd/iliffe/i_phpinfo.php > > f: /httpd/iliffe/i_phpinfo.php > > > > dr-xr-xr-x / > > drwxr-xr-x httpd > > drwxr-xr-x iliffe > > -rw-r--r-- i_phpinfo.php > > > > ---------------------- > > There's something odd about that code/logging (no parameter on the > open call repesenting the name!) Can you strace the FPM process and > see what it actually tries to open? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|