From 25f0f3cb37c76a863aa1c5b1e6b2be198215fdfb Mon Sep 17 00:00:00 2001 From: Jack Pearkes Date: Fri, 31 Jul 2015 12:14:28 -0700 Subject: [PATCH] website: fix broken link on acl page --- website/source/docs/internals/acl.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/internals/acl.html.markdown b/website/source/docs/internals/acl.html.markdown index c1daa63738..d661bca1f0 100644 --- a/website/source/docs/internals/acl.html.markdown +++ b/website/source/docs/internals/acl.html.markdown @@ -42,7 +42,7 @@ automatically applied: this allows policy to be enforced on legacy clients. Enforcement is always done by the server nodes. All servers must be configured to provide an [`acl_datacenter`](/docs/agent/options.html#acl_datacenter) which enables ACL enforcement but also specifies the authoritative datacenter. Consul does not -replicate data cross-WAN and instead relies on [RPC forwarding](/docs/internal/architecture.html) +replicate data cross-WAN and instead relies on [RPC forwarding](/docs/internals/architecture.html) to support Multi-Datacenter configurations. However, because requests can be made across datacenter boundaries, ACL tokens must be valid globally. To avoid replication issues, a single datacenter is considered authoritative and stores