From 35702fed462f63a0a237cfbfdf26184272207c11 Mon Sep 17 00:00:00 2001 From: alyssawilk Date: Tue, 2 Jun 2020 15:21:34 -0400 Subject: [PATCH] docs: fixing broken link (#11406) Signed-off-by: Alyssa Wilk --- bazel/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bazel/README.md b/bazel/README.md index 237fb7bfc3eb..9bad8cf1431a 100644 --- a/bazel/README.md +++ b/bazel/README.md @@ -532,7 +532,7 @@ The following optional features can be enabled on the Bazel build command-line: * Perf annotation with `--define perf_annotation=enabled` (see source/common/common/perf_annotation.h for details). * BoringSSL can be built in a FIPS-compliant mode with `--define boringssl=fips` - (see [FIPS 140-2](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/ssl.html#fips-140-2) for details). + (see [FIPS 140-2](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2) for details). * ASSERT() can be configured to log failures and increment a stat counter in a release build with `--define log_debug_assert_in_release=enabled`. The default behavior is to compile debug assertions out of release builds so that the condition is not evaluated. This option has no effect in debug builds.