On Tue, Jun 25, 2024 at 5:22 PM Eric Covener <cove...@gmail.com> wrote: > > On Tue, Jun 25, 2024 at 5:06 PM Eric Covener <cove...@gmail.com> wrote: > > > > On Tue, Jun 25, 2024 at 4:35 PM Helmut K. C. Tessarek > > <tessa...@evermeet.cx> wrote: > > > > > > On 2024-06-25 02:53, Ruediger Pluem wrote: > > > > Can you provide more details on your configuration how you forward > > > > stuff to fcgi and what request you made? > > > > > > Very simple: > > > > > > <FilesMatch "\.php$"> > > > SetHandler "proxy:unix:/run/php82-fpm/xxx.sock|fcgi://xxx" > > > </FilesMatch> > > > > I think this new path needs to account for UDS. The URL is e.g. > > "unix:/tmp/fake.sock|fcgi://xxx..." during proxy_fcgi_canon so it > > declines, then the core handler reports the error on the > > pseudo-filename. > > Or for now, skip the newly added proxy_fixup() and escape just > r->filename before it gets the handler prefixed to it?
These all seem hairy. We can do something more targetted from the start to decrease the fallout? -- Eric Covener cove...@gmail.com
