Nginx Series Tutorials: Nginxhttpownermatch modules (resolve linked file cross-station access)

Overview

The module provides a simple file based on owner's http://www.aliyun.com/zixun/aggregation/38609.html "> access control."

The Nginx_http_owner_match_module module allows it to control the access of specific files to the owner and organization.

Access rule checks are based on the order in which they are declared.

Configuration Example:

Location/{
Omallow Heiher; # Allow access files of Heiher
Omallow Jack Sftp; # Allow access files of jack:sftp
Omdeny all; # Deny Others
}

Instructions

Omallow

Syntax: Omallow [username | username GroupName | all]
Default value: No
Scopes: HTTP, server, location, limit_except
This directive is used to access the specified user name or user group.

Omdeny

Syntax: Deny [username | username GroupName | all]
Default value: No
Scopes: HTTP, server, location, limit_except
This directive is used to prevent access to the specified user name or user group.

Resources

Nginx Module HTTP Ownermatch

I wrote a Nginx module, HTTP Ownermatch, that solves the problem of Nginx between virtual hosts that can be accessed through linked files (hard links and symbolic links). This module allows you to specify which user files each Location can or cannot access for each virtual host.

Configuration file Instance

Location/{
root HTML;
Index index.html index.htm;
Omallow Heiher; # Allow access to files attached to Heiher
Omallow guest sftp; # Allow access to files attached to Guest:sftp
Omdeny all; # do not allow access to any other files
}

Source Code Warehouse

git clone git://gitcafe.com/heiher/nginx.git