nginx.git/conf/fastcgi_params, branch release-1.17.3 nginx Added the REQUEST_SCHEME parameter. 2015-06-05T19:23:26+00:00 Maxim Dounin mdounin@mdounin.ru 2015-06-05T19:23:26+00:00 413158330abf082d1c0b48b264090f3bf4e4305e The REQUEST_SCHEME parameter was introduced in Apache 2.3.11 and seems to be used by some scripts now. It looks more logical than previously used HTTPS. 
The REQUEST_SCHEME parameter was introduced in Apache 2.3.11 and seems
to be used by some scripts now.  It looks more logical than previously
used HTTPS.
Added HTTPS param with Apache-like behaviour to fastcgi/scgi/uwsgi_params (fixes #38). 2011-12-09T15:38:26+00:00 Valentin Bartenev vbart@nginx.com 2011-12-09T15:38:26+00:00 fd87f1b7906120b81dba06558d73ed492f2a230f 






add $nginx_version
2007-07-22T13:15:21+00:00

Igor Sysoev
igor@sysoev.ru

2007-07-22T13:15:21+00:00

17cf33f830134025dd8111d1aa00cca6154c07ca












nginx-0.1.43-RELEASE import
2005-08-30T10:55:07+00:00

Igor Sysoev
igor@sysoev.ru

2005-08-30T10:55:07+00:00

e5035397b01ec12f351a6a984f83091b821978cc

    *) Feature: the listen(2) backlog in the "listen" directive can be
       changed using the -HUP signal.

    *) Feature: the geo2nginx.pl script was added to contrib.

    *) Change: the FastCGI parameters with the empty values now are passed
       to a server.

    *) Bugfix: the segmentation fault occurred or the worker process may
       got caught in an endless loop if the proxied or FastCGI server sent
       the "Cache-Control" header line and the "expires" directive was
       used; in the proxied mode the the bug had appeared in 0.1.29.





    *) Feature: the listen(2) backlog in the "listen" directive can be
       changed using the -HUP signal.

    *) Feature: the geo2nginx.pl script was added to contrib.

    *) Change: the FastCGI parameters with the empty values now are passed
       to a server.

    *) Bugfix: the segmentation fault occurred or the worker process may
       got caught in an endless loop if the proxied or FastCGI server sent
       the "Cache-Control" header line and the "expires" directive was
       used; in the proxied mode the the bug had appeared in 0.1.29.