On Wed, Feb 8, 2017 at 3:31 PM, Jim Jagielski <[email protected]> wrote: > I have. With PHP-FPM as well as that Perl script FPM. All works > as expected.
In my env, the change doesn't result in any change to SCRIPT_NAME. I only test w/ the perl script and use *.phx vs *.php to see both paths. AcceptPathInfo ON AddType application/x-php7-fpm .php Action application/x-php7-fpm /fpm virtual <Location /fpm> SetHandler "proxy:fcgi://localhost:12345" </Location> <FilesMatch \.phx$> SetHandler "proxy:fcgi://127.0.0.1:12345" </FilesMatch> If I hit /info.phx/path.info, SCRIPT_NAME is /info.phx and stays that way. If I hit /info.php/path/info, SCRIPT_NAME starts /fpm and stays that way (if using FPM, it would see REDIRECT_* and figure out our real paths) (added orig string to trace locally): [Thu Feb 09 03:47:01.331270 2017] [proxy_fcgi:trace4] [pid 26390:tid 139707007817472] mod_proxy_fcgi.c(392): [client 127.0.0.1:43100] fpm:virtual_script: Modified SCRIPT_NAME from /info.phx to: /info.phx [Thu Feb 09 03:49:54.050047 2017] [proxy_fcgi:trace4] [pid 26390:tid 139706991032064] mod_proxy_fcgi.c(392): [client 127.0.0.1:43168] fpm:virtual_script: Modified SCRIPT_NAME from /fpm to: /fpm Assuming there's some alternate path that actually does change SCRIPT_NAME by default, we a) don't have any complaint about SCRIPT_NAME and b) have the SetEnv thing. If we want more options, maybe we can stash this older SCRIPT_NAME into a new variable and show how to copy it over SCRIPT_NAME? -- Eric Covener [email protected]
