I'm testing your recent config and the config from https://github.com/apache/httpd/commit/cab0bfbb2645bb8f689535e5e2834e2dbc23f5a5#commitcomment-20393588 w/ htaccess that makes index.php act like a front controller. Lately I look at the output of the fakefpm.pl script I posted above, but was originally pointing at a simple fpm server.
But since it's a 2.4.23 regression for fpm, I am looking for the minimum change, because there are just too many potential fastcgi servers we could be contacting. IOW why make other tweaks here w/o opt-in if the only report we have is the guy who is broken by the fcgi:// stripping? I'm just afraid we won't see the problems in synthetic tests. On Wed, Jan 25, 2017 at 11:37 PM, Eric Covener <[email protected]> wrote: > Seems like w/ the update it's still a bogus PATH_INFO that fpm is correcting > > 'PATH_INFO' => '/foo.php/bar/baz/', > > I'm using this as the target from one of the old bug reports. > > #!/usr/bin/perl > use FCGI; > use Socket; > use FCGI::ProcManager; > use Data::Dumper; > > $num_args = $#ARGV + 1; > if ($num_args != 1) { > print "\nUsage: fcgi.pl <socket>\n"; > exit 1; > } > > $proc_manager = FCGI::ProcManager->new( {n_processes => 1} ); > $socket = FCGI::OpenSocket( $ARGV[0], 10 ); > $request = FCGI::Request( \*STDIN, \*STDOUT, \*STDERR, \%req_params, > $socket, &FCGI::FAIL_ACCEPT_ON_INTR ); > $proc_manager->pm_manage(); > if ($request) { > while ( $request->Accept() >= 0 ) { > $proc_manager->pm_pre_dispatch(); > print("Content-type: text/plain\r\n\r\n"); > print Dumper(\%req_params); > } > } > FCGI::CloseSocket($socket); > > On Wed, Jan 25, 2017 at 11:31 PM, Jim Jagielski <[email protected]> wrote: >> OK... I just committed something that in the AddType/Action >> setup has reasonable values w/ php-fpm70 > > > > -- > Eric Covener > [email protected] -- Eric Covener [email protected]
