squid:acls:acl_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| squid:acls:acl_types [2020/04/04 16:02] – [maxconn] peter | squid:acls:acl_types [2020/07/15 09:30] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 765: | Line 765: | ||
| ===== max_user_ip ===== | ===== max_user_ip ===== | ||
| - | This will be matched when the same user attempts to log in for more than the specified number of times from different | + | This will be matched when the same user attempts to log in for more than the specified number of times from different |
| If -s is specified then the limit is strict, denying browsing from any further IP addresses until the ttl has expired. | If -s is specified then the limit is strict, denying browsing from any further IP addresses until the ttl has expired. | ||
| - | Without -s Squid will just annoy the user by " | + | Without -s Squid will just annoy the user by " |
| - | The authenticate_ip_ttl parameter controls the timeout on the ip entries. | + | The authenticate_ip_ttl parameter controls the timeout on the IP entries. |
| <WRAP info> | <WRAP info> | ||
| **NOTE:** | **NOTE:** | ||
| - | 1. Any authentication program must be running for this. NCSA will a simple configuration. | + | 1. Any authentication program must be running for this. NCSA will a simple configuration. |
| 2. In acceleration mode or where there is mesh of child proxies, clients may appear to come from multiple addresses if they are going through proxy farms, so a limit of 1 may cause user problems. | 2. In acceleration mode or where there is mesh of child proxies, clients may appear to come from multiple addresses if they are going through proxy farms, so a limit of 1 may cause user problems. | ||
| </ | </ | ||
| Line 789: | Line 790: | ||
| * **number**: | * **number**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
| Line 816: | Line 817: | ||
| * **mime_type**: | * **mime_type**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
| Line 833: | Line 834: | ||
| ===== req_header ===== | ===== req_header ===== | ||
| - | |||
| - | Match against any of the known request headers. | ||
| Regular Expression match against any of the known request headers. | Regular Expression match against any of the known request headers. | ||
| Line 849: | Line 848: | ||
| * **header-name**: | * **header-name**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
| Line 863: | Line 862: | ||
| Match against the mime type of the reply received by Squid. | Match against the mime type of the reply received by Squid. | ||
| - | ~Also, using this, you can detect file download or some types HTTP tunneling requests. | + | Using this, you can detect file download or some types HTTP tunneling requests. |
| - | This has no effect in **http_access** rules. | + | This has no effect in **http_access** rules. |
| < | < | ||
| Line 876: | Line 875: | ||
| * **mime_type**: | * **mime_type**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
| Line 888: | Line 887: | ||
| ===== rep_header ===== | ===== rep_header ===== | ||
| - | |||
| - | Match against any of the known response headers. | ||
| Regular Expression match against any of the known response headers. | Regular Expression match against any of the known response headers. | ||
| Line 902: | Line 899: | ||
| * **header-name**: | * **header-name**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
| Line 923: | Line 920: | ||
| * **class_name**: | * **class_name**: | ||
| - | Example(s) | + | Example: |
| < | < | ||
squid/acls/acl_types.1586016137.txt.gz · Last modified: 2020/07/15 09:30 (external edit)