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

Nginx Path-based client-side TLS verification

· 52CE 我爱测

I have googled around and it seems like nginx does not provide a way to do client-side TLS verification based on the path. I just wanted to ask the community if this is still the case, or if there is some sort of a work around. I…

问题原文

原帖链接 · Keeto · CC BY-SA 3.0

I have googled around and it seems like nginx does not provide a way to do client-side TLS verification based on the path. I just wanted to ask the community if this is still the case, or if there is some sort of a work around.

I am basically trying to have an admin page domain-name/admin where accessing the public domain name requires only server-side TLS verification but I want to have mutual TLS verification only for the /admin path. Is this even possible without having to get a new domain for admin?

社区高分解答

原帖链接 · Adrien · CC BY-SA 3.0

The reason for this is because nginx doesn't learn the path (part of the request) until after the TLS layer is set up, so it can't go back in time and change its mind about requiring a client cert.

Another work-around may be to redirect /admin to another hostname e.g.admin.domain-name (you'd need a wild-card cert), and then it should be able to enforce client certs at that level.

Otherwise if you try making the client cert optional, every client will get a dialog popup asking them to choose a client cert.

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

资料来源与适用范围

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

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

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