The only information I got on the Web was to protect folders with Nginx
auth, just like the plein old Apache’s .htaccess.
I am already using AuthPlain to secure a folder with Nginx, using PHP
scripts inside.
I wonder if it was possible to use Nginx auth information inside those
PHP
scripts.
More precisely, I would have a directory protected with AuthPlain and I
would have a script (let’s call it index.php) being called when the
authentication is successful.
The AuthPlain has several users registered and I would like to know if
index.php might be aware who logged in to welcom him with his/her
username.
Thanks to both of you, I got the info I was seeking for.
However, when I try to activate the fastcgi_param, the content doesn’t
seem
to reach PHP anymore.
No error logged neither in Nginx nor PHP it seems.
I feel like I am a noob… oO
server {
listen 80;
server_name ~ab.cd$;
root /var/web/$host;
index index.html index.php;
try_files $uri $uri/ =404;
access_log /var/log/nginx/ab.cd/access.log main;
error_log /var/log/nginx/ab.cd/error.log warn;
include conf.d/includes/fastcgi.conf;
auth_basic “Get out!”;
auth_basic_user_file /var/web/ab.cd.htpasswd;
location ~ \.php$ {
fastcgi_pass unix:/var/run/php-fpm.sock;
#If the following is activated, no more PHP output...
Now I think I got it all.
Well it was non-sense to put fastcgi out of the PHP location anyway…
but
I didn’t know about the environment problem.
I’ll try to think about that next time something I play with Nginx
configuration.
On Tue, Feb 26, 2013 at 05:26:49PM -0500, B.R. wrote:
I feel like I am a noob… oO
The problem is due to how nginx directives are inherited to different
levels. It’s consistent within nginx, so once you learn it you can apply
it to all directives which inherit.
Just put your new fastcgi_param directive at the same level as the
others
(which are in the “include” file).