diff --git a/docs/content/deploy/amazon-api-gw.md b/docs/content/deploy/amazon-api-gw.md index 150cafbd4..c7eb64f3b 100644 --- a/docs/content/deploy/amazon-api-gw.md +++ b/docs/content/deploy/amazon-api-gw.md @@ -35,4 +35,4 @@ generated certificate you need to configure the `aws.apigw.cert.cn` as follows: `api-gw-cert.pem` is the certificate generated in the AWS Management Console. `your/cert.pem` and `your/key.pem` is the certificate/key pair for the HTTPS certificate. Since the Amazon API Gateway certificates don't have the `CA` flag set fabio needs to trust them for the client certificate authentication to work. Otherwise, you will get an `TLS handshake error: failed to verify client's certificate`. See [Issue 108](/eBay/fabio/issues/108) for details. -**Note:** The `aws.apigw.cert.cn` parameter will not be supported in version 1.2 and later which support dynamic certificate stores. You will have to add the `caupgcn=ApiGateway` parameter to the certificate source configuration instead. See [Certificate Stores](/#certificate-stores) for more detail. +**Note:** The `aws.apigw.cert.cn` parameter will not be supported in version 1.2 and later which support dynamic certificate stores. You will have to add the `caupgcn=ApiGateway` parameter to the certificate source configuration instead. See [Certificate Stores](/feature/certificate-stores/) for more detail. diff --git a/docs/content/feature/tcp-proxy.md b/docs/content/feature/tcp-proxy.md index db01fc694..0957a9c7c 100644 --- a/docs/content/feature/tcp-proxy.md +++ b/docs/content/feature/tcp-proxy.md @@ -12,7 +12,7 @@ Consul. In addition, fabio needs to be configured to listen on that port: fabio -proxy.addr ':1234;proto=tcp' ``` -TCP proxy support can be combined with [Certificate Stores](./certificate-stores) to provide TLS termination on fabio. +TCP proxy support can be combined with [Certificate Stores](/feature/certificate-stores/) to provide TLS termination on fabio. ``` fabio -proxy.cs 'cs=ssl;type=path;path=/etc/ssl' -proxy.addr ':1234;proto=tcp;cs=ssl'