aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Jakob Buchgraber <buchgr@google.com>2018-02-08 12:19:57 -0800
committerGravatar Copybara-Service <copybara-piper@google.com>2018-02-08 12:21:43 -0800
commitcf3f81aef7c32019d70cbce218a64a03276268f0 (patch)
tree91e53806bed5441f4e93c43c999ac1ace3ce0c8f /site
parent1c6d061ea448ee19022f6e609099515a25a5a131 (diff)
remote: Add support for HTTP Basic Auth
Closes #4609. PiperOrigin-RevId: 185032751
Diffstat (limited to 'site')
-rw-r--r--site/docs/remote-caching.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/site/docs/remote-caching.md b/site/docs/remote-caching.md
index bfdf4e7b87..0d193dd85f 100644
--- a/site/docs/remote-caching.md
+++ b/site/docs/remote-caching.md
@@ -19,6 +19,7 @@ make builds significantly faster.
* [Bazel Remote Cache](#bazel-remote-cache)
* [Google Cloud Storage](#google-cloud-storage)
* [Other servers](#other-servers)
+* [Authentication](#authentication)
* [HTTP Caching Protocol](#http-caching-protocol)
* [Run Bazel using the remote cache](#run-bazel-using-the-remote-cache)
* [Read from and write to the remote cache](#read-from-and-write-to-the-remote-cache)
@@ -174,6 +175,14 @@ You can set up any HTTP/1.1 server that supports PUT and GET as the cache's
backend. Users have reported success with caching backends such as [Hazelcast],
[Apache httpd], and [AWS S3].
+## Authentication
+
+As of version 0.11.0 support for HTTP Basic Authentication was added to Bazel.
+You can pass a username and password to Bazel via the remote cache URL. The
+syntax is `https://username:password@hostname.com:port/path`. Please note that
+HTTP Basic Authentication transmits username and password in plaintext over the
+network and it's thus critical to always use it with HTTPS.
+
## HTTP Caching Protocol
Bazel supports remote caching via HTTP/1.1. The protocol is conceptually simple: