You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 17, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# RabbitMQ Access Control Cache Plugin
2
2
3
-
This plugin provides a caching layer for [access control operations](http://rabbitmq.com/access-control.html)
3
+
This plugin provides a caching layer for [access control operations](https://rabbitmq.com/access-control.html)
4
4
performed by RabbitMQ nodes.
5
5
6
6
## Project Maturity
@@ -9,14 +9,14 @@ As of 3.7.0, this plugin is distributed with RabbitMQ.
9
9
10
10
## Overview
11
11
12
-
This plugin provides a way to cache [authentication and authorization backend](http://rabbitmq.com/access-control.html)
12
+
This plugin provides a way to cache [authentication and authorization backend](https://rabbitmq.com/access-control.html)
13
13
results for a configurable amount of time.
14
14
It's not an independent auth backend but a caching layer for existing backends
15
15
such as the built-in, [LDAP](github.com/rabbitmq/rabbitmq-auth-backend-ldap), or [HTTP](github.com/rabbitmq/rabbitmq-auth-backend-http)
16
16
ones.
17
17
18
18
Cache expiration is currently time-based. It is not very useful with the built-in
19
-
(internal) [authn/authz backends](http://rabbitmq.com/access-control.html) but can be very useful for LDAP, HTTP or other backends that
19
+
(internal) [authn/authz backends](https://rabbitmq.com/access-control.html) but can be very useful for LDAP, HTTP or other backends that
20
20
use network requests.
21
21
22
22
## RabbitMQ Version Requirements
@@ -38,7 +38,7 @@ Binary builds can be obtained [from project releases](https://github.com/rabbitm
38
38
## Building
39
39
40
40
You can build and install it like any other plugin (see
41
-
[the plugin development guide](http://www.rabbitmq.com/plugin-development.html)).
41
+
[the plugin development guide](https://www.rabbitmq.com/plugin-development.html)).
42
42
43
43
## Authentication and Authorization Backend Configuration
44
44
@@ -51,7 +51,7 @@ So a configuration fragment that enables this plugin *only* (this example is **i
51
51
52
52
auth_backends.1 = cache
53
53
54
-
In the [classic config format](http://www.rabbitmq.com/configure.html#config-file-formats):
54
+
In the [classic config format](https://www.rabbitmq.com/configure.html#config-file-formats):
55
55
56
56
```erlang
57
57
[
@@ -170,7 +170,7 @@ define `start_link` function to start cache process.
170
170
This repository provides several implementations:
171
171
172
172
*`rabbit_auth_cache_dict` stores cache entries in the internal process dictionary. **This module is for demonstration only and should not be used in production**.
173
-
*`rabbit_auth_cache_ets` stores cache entries in an [ETS](http://learnyousomeerlang.com/ets) table and uses timers for cache invalidation. **This is the default implementation**.
173
+
*`rabbit_auth_cache_ets` stores cache entries in an [ETS](https://learnyousomeerlang.com/ets) table and uses timers for cache invalidation. **This is the default implementation**.
174
174
*`rabbit_auth_cache_ets_segmented` stores cache entries in multiple ETS tables and does not delete individual cache items but rather
175
175
uses a separate process for garbage collection.
176
176
*`rabbit_auth_cache_ets_segmented_stateless` same as previous, but with minimal use of `gen_server` state, using ets tables to store information about segments.
@@ -183,7 +183,7 @@ Cache module can be set via sysctl config format:
Additional cache module arguments can only be defined via the [advanced config](http://www.rabbitmq.com/configure.html#advanced-config-file) or classic config format:
186
+
Additional cache module arguments can only be defined via the [advanced config](https://www.rabbitmq.com/configure.html#advanced-config-file) or classic config format:
0 commit comments