Wrong documentation about fastcgi_param...

[Dimitri]

Hi Maxim,

yes sorry, it's the wrong mailing-list.

I've got it wrong.
I thought, that the current level only overwrite the specified parameters
and takes the other parameters from the global level(which makes more sense to me).

However, sorry for the misplaced post and thanks for the clarification.




Gesendet mittels einer sicheren E-Mail von Proton Mail.
------- Original Message -------
Maxim Dounin <mdounin at mdounin.ru> schrieb am Sonntag, 29. Mai 2022 um 03:45:


> Hello!
>
> On Sat, May 28, 2022 at 12:38:45PM +0000, Dimitri via nginx-devel wrote:
>
> > Hi,
> >
> > for a few hours yesterday i've had the Problem "FastCGI sent in
> > stderr: "Primary script unknown" while reading response header
> > from upstream".
> >
> > I use PHP-FPM with chroot and know about the
> > configuration-problems with wrong "fastcgi_param SCRIPT_FILENAME
> > ...", which you can find on the internet.
>
>
> [...]
>
> > But these directive WAS SET in the example.conf, so why nginx
> > does not behave as stated in the docs?
> > Why nginx uses the global SCRIPT_FILENAME-setting, although
> > these setting is on the "current level" in example.conf?
>
>
> The nginx-devel@ mailing list is to discuss nginx development. If
> don't want to suggest a patch, but rather need help with
> understanding what goes wrong in your nginx configuration and how
> to configure nginx properly, please use the nginx@ mailing list
> instead.
>
> (Note though that you may want to provide more details - in
> particular, full configuration you are trying to use. Note well
> that the location configuration you've tried to use will only send
> the SCRIPT_FILENAME param to PHP, without any other parameters.
> This will certainly break PHP-FPM, but will result in 200 with an
> empty body, not 404. So probably there is more than one issue in
> your configuration.)
>
> Thank you.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx-devel mailing list -- nginx-devel at nginx.org
> To unsubscribe send an email to nginx-devel-leave at nginx.org