On Fri, May 1, 2020, 17:21 @lbutlr <krem...@kreme.com> wrote: > On 01 May 2020, at 08:52, Rich Bowen <rbo...@rcbowen.com> wrote: > > On 4/30/20 6:08 PM, @lbutlr wrote: > >> I'm trying to troubleshoot a Domain that is loading the wrong content > (Well, I am sure it is loading the RIGHT content, but not the INTENED > content) and was wondering if there is a flag for apachectl that will show > me what apache thinks the document root is for each vhost? And possibly a > way of piping in a URL and having apache spit back where that URL points to > locally and the steps taken to get there (redirect, proxy, lookup, > whatever). > >> A trace, essentially. > > > > > > Not directly, but > > > > httpd -t -D DUMP_VHOSTS > > > > is a good start. It at least tells you what names are handled by what > bits of the configuration file(s). > > Yeah, but it dodoesn’t show the path that apache takes to load a page, > which is what I am looking for. > > For example, the issue that I had turned out to be that since > DirectoryIndex globally contains index.php, the fcgi was triggering even > when there was no index.php file present instead of loading the index.html. > Either setting DirectoryIndex locally or disabling the fcgi resulted in the > expected page loading. > > That wasn’t discoverable by looking at the configuration until I thought, > “Huh, I wonder…” > > Seems there would be some tool out there that would do this as it must be > someone else has thought of for troubleshooting, >
While that would be incredibly cool, I'm not aware of any such tool. On the other hand, adding a bunch of additional debug level prints in the URL mapping modules would serve the same purpose. But, again, that doesn't exist at this time, as far as I'm aware. >
