Thanks Eric: That is probably what is happening (now). There is a fairly obvious solution to this problem then, just set up a JavaScript href=... switch using the original page and let the browser request the proper one. Is there a general work around for this sort of situation that will cause the proper handler to be used?
Thanks again for everything. John ========= On Sat, 2022-12-03 at 20:57 -0500, Eric Covener wrote: > > It appears that php-fpm didn't get a whack at the page before it was served, > > even though the page is valid and the extension is ".php". It would seem > > that > > Apache treated the page using the initial extension (.html) instead of the > > linked page extension (.php) > > Apache doesn't use the link target in the way you expect (it is not > fed back into config sections like Directory or Files/FilesMatch) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
