proftp 파일업로드 제한
페이지 정보
작성자 MintState 댓글 0건 조회 16,274회 작성일 08-12-04 22:11본문
proftp 파일업로드 제한
** MaxStoreFileSize **
Syntax : MaxStoreFileSize [ number|"*" units "user"|"group"|"class" expression]]
Default : None
Context : server config, <Global>, <VirtualHost>, <Anonymous>, <Directory>, .ftpaccess Compatibility : 1.2.7rc1 and later, and requried mod_xfer
When uploading files from a client (eg serving a STOR request), the server will check for any configured limit against the size of the file being sent, and abort any transfers if/when the given file's size exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used primarily to override any inherited restrictions from higher contexts. The given number is the number of bytes for the limit, and is followed by a units specifier of (case-insensitive) "Gb" (Gigabytes), "Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes).
The given number of bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only to specific users. If the "user" restriction is given, then expression is a user-expression specifying to which users the rule applies. Similarly for the "group" restriction. For the "class" restriction, the expression is simply the name of connection class for whom the rule will apply. If no matching user, group, or class expression is found for the current user (in that order), then a limit with no expression (ie no "user", "group", or "class" identifier) is applied.
Examples :
----------------------------------------------------------------------
** MaxRetrieveFileSize **
Syntax : MaxRetrieveFileSize [ number|"*" units "user"|"group"|"class" expression]]
Default : None
Context server config, <Global>, <VirtualHost>, <Anonymous>, <Directory>, .ftpaccess
Compatibility : 1.2.7rc1 and later, and required mod_xfer
When downloading files to clients (eg serving a RETR request), the server will check for any configured limit against the size of the file being requested, and abort any transfers if the requested file's size exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used primarily to override any inherited restrictions from higher contexts. The given number is the number of bytes for the limit, and is followed by a units specifier of (case-insensitive) "Gb" (Gigabytes), "Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes).
The given number of bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only to specific users. If the "user" restriction is given, then expression is a user-expression specifying to which users the rule applies. Similarly for the "group" restriction. For the "class" restriction, the expression is simply the name of connection class for whom the rule will apply. If no matching user, group, or class expression is found for the current user (in that order), then a limit with no expression (i.e. no "user", "group", or "class" identifier) is applied.
Examples :
** MaxStoreFileSize **
Syntax : MaxStoreFileSize [ number|"*" units "user"|"group"|"class" expression]]
Default : None
Context : server config, <Global>, <VirtualHost>, <Anonymous>, <Directory>, .ftpaccess Compatibility : 1.2.7rc1 and later, and requried mod_xfer
When uploading files from a client (eg serving a STOR request), the server will check for any configured limit against the size of the file being sent, and abort any transfers if/when the given file's size exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used primarily to override any inherited restrictions from higher contexts. The given number is the number of bytes for the limit, and is followed by a units specifier of (case-insensitive) "Gb" (Gigabytes), "Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes).
The given number of bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only to specific users. If the "user" restriction is given, then expression is a user-expression specifying to which users the rule applies. Similarly for the "group" restriction. For the "class" restriction, the expression is simply the name of connection class for whom the rule will apply. If no matching user, group, or class expression is found for the current user (in that order), then a limit with no expression (ie no "user", "group", or "class" identifier) is applied.
Examples :
----------------------------------------------------------------------
** MaxRetrieveFileSize **
Syntax : MaxRetrieveFileSize [ number|"*" units "user"|"group"|"class" expression]]
Default : None
Context server config, <Global>, <VirtualHost>, <Anonymous>, <Directory>, .ftpaccess
Compatibility : 1.2.7rc1 and later, and required mod_xfer
When downloading files to clients (eg serving a RETR request), the server will check for any configured limit against the size of the file being requested, and abort any transfers if the requested file's size exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used primarily to override any inherited restrictions from higher contexts. The given number is the number of bytes for the limit, and is followed by a units specifier of (case-insensitive) "Gb" (Gigabytes), "Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes).
The given number of bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only to specific users. If the "user" restriction is given, then expression is a user-expression specifying to which users the rule applies. Similarly for the "group" restriction. For the "class" restriction, the expression is simply the name of connection class for whom the rule will apply. If no matching user, group, or class expression is found for the current user (in that order), then a limit with no expression (i.e. no "user", "group", or "class" identifier) is applied.
Examples :
|
댓글목록
등록된 댓글이 없습니다.