大网数据广告活动
服务器运维问答

HTTP .htpasswd protect sub-domain on Nginx recursively

· 52CE 我爱测

I want to password protect my developer subdomain (dev.example.com), and leave the main domain publicly available. I want to do this recursively, so that any file or folder on the subdomain will always prompt you for a login. In …

问题原文

原帖链接 · Trace DeCoy · CC BY-SA 3.0

I want to password protect my developer subdomain (dev.example.com), and leave the main domain publicly available.

I want to do this recursively, so that any file or folder on the subdomain will always prompt you for a login.

In the Nginx config file, I've added the following to my dev.example.com server-block (note that I have separate server-blocks for the main and subdomain):

location ^~ / {
    auth_basic "Administrator Login";
    auth_basic_user_file /home/path/to/.htpasswd;
}

From searching around on SF, I was under the impression that the ^~ identifier makes the password protection recursive, but it doesn't.

While dev.example.com specifically prompts me for a login, dev.example.com/folder/ doesn't.

What am I doing wrong?

已采纳解答

原帖链接 · Richard Smith · CC BY-SA 3.0

To protect the entire subdomain, the statements should appear in the existing server block:

server {
    server_name dev.example.com;
    auth_basic "Administrator Login";
    auth_basic_user_file /home/path/to/.htpasswd;
    ...
}

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-01-12)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。