X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/27b9247e0c42700e0c7d94f7721e2164610b1e4c..9cc572d6a44262e21251372e28b549cfc09e681a:/services/keep-web/doc.go diff --git a/services/keep-web/doc.go b/services/keep-web/doc.go index 4207d7bfc7..d65156f987 100644 --- a/services/keep-web/doc.go +++ b/services/keep-web/doc.go @@ -1,26 +1,46 @@ -// Keep-web provides read-only HTTP access to files stored in Keep. It -// serves public data to anonymous and unauthenticated clients, and -// serves private data to clients that supply Arvados API tokens. It -// can be installed anywhere with access to Keep services, typically -// behind a web proxy that supports TLS. +// Copyright (C) The Arvados Authors. All rights reserved. +// +// SPDX-License-Identifier: AGPL-3.0 + +// Keep-web provides read/write HTTP (WebDAV) access to files stored +// in Keep. It serves public data to anonymous and unauthenticated +// clients, and serves private data to clients that supply Arvados API +// tokens. It can be installed anywhere with access to Keep services, +// typically behind a web proxy that supports TLS. // // See http://doc.arvados.org/install/install-keep-web.html. // -// Run "keep-web -help" to show all supported options. +// Configuration +// +// The default configuration file location is +// /etc/arvados/keep-web/keep-web.yml. +// +// Example configuration file +// +// Client: +// APIHost: "zzzzz.arvadosapi.com:443" +// AuthToken: "" +// Insecure: false +// Listen: :1234 +// AnonymousTokens: +// - xxxxxxxxxxxxxxxxxxxx +// AttachmentOnlyHost: "" +// TrustAllContent: false // // Starting the server // -// Serve HTTP requests at port 1234 on all interfaces: +// Start a server using the default config file +// /etc/arvados/keep-web/keep-web.yml: // -// keep-web -listen=:1234 +// keep-web // -// Serve HTTP requests at port 1234 on the interface with IP address 1.2.3.4: +// Start a server using the config file /path/to/keep-web.yml: // -// keep-web -listen=1.2.3.4:1234 +// keep-web -config /path/to/keep-web.yml // // Proxy configuration // -// Keep-web does not support SSL natively. Typically, it is installed +// Keep-web does not support TLS natively. Typically, it is installed // behind a proxy like nginx. // // Here is an example nginx configuration. @@ -48,12 +68,12 @@ // // Anonymous downloads // -// Use the -allow-anonymous flag with an ARVADOS_API_TOKEN environment -// variable to specify a token to use when clients try to retrieve -// files without providing their own Arvados API token. +// The "AnonymousTokens" configuration entry is an array of tokens to +// use when processing anonymous requests, i.e., whenever a web client +// does not supply its own Arvados API token via path, query string, +// cookie, or request header. // -// export ARVADOS_API_TOKEN=zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz -// keep-web [...] -allow-anonymous +// "AnonymousTokens":["xxxxxxxxxxxxxxxxxxxxxxx"] // // See http://doc.arvados.org/install/install-keep-web.html for examples. // @@ -113,8 +133,21 @@ // http://zzzzz-4zz18-znfnqtbbv4spc3w.collections.example.com/foo/bar.txt // http://zzzzz-4zz18-znfnqtbbv4spc3w.collections.example.com/_/foo/bar.txt // http://zzzzz-4zz18-znfnqtbbv4spc3w--collections.example.com/_/foo/bar.txt +// +// The following URLs are read-only, but otherwise interchangeable +// with the above: +// // http://1f4b0bc7583c2a7f9102c395f4ffc5e3-45--foo.example.com/foo/bar.txt // http://1f4b0bc7583c2a7f9102c395f4ffc5e3-45--.invalid/foo/bar.txt +// http://collections.example.com/by_id/1f4b0bc7583c2a7f9102c395f4ffc5e3%2B45/foo/bar.txt +// http://collections.example.com/by_id/zzzzz-4zz18-znfnqtbbv4spc3w/foo/bar.txt +// +// If the collection is named "MyCollection" and located in a project +// called "MyProject" which is in the home project of a user with +// username is "bob", the following read-only URL is also available +// when authenticating as bob: +// +// http://collections.example.com/users/bob/MyProject/MyCollection/foo/bar.txt // // An additional form is supported specifically to make it more // convenient to maintain support for existing Workbench download @@ -128,6 +161,9 @@ // // http://collections.example.com/collections/uuid_or_pdh/foo/bar.txt // +// Collections can also be accessed (read-only) via "/by_id/X" where X +// is a UUID or portable data hash. +// // Authorization mechanisms // // A token can be provided in an Authorization header: @@ -158,11 +194,10 @@ // // Indexes // -// Currently, keep-web does not generate HTML index listings, nor does -// it serve a default file like "index.html" when a directory is -// requested. These features are likely to be added in future -// versions. Until then, keep-web responds with 404 if a directory -// name (or any path ending with "/") is requested. +// Keep-web returns a generic HTML index listing when a directory is +// requested with the GET method. It does not serve a default file +// like "index.html". Directory listings are also returned for WebDAV +// PROPFIND requests. // // Compatibility // @@ -211,25 +246,37 @@ // only when the designated origin matches exactly the Host header // provided by the client or downstream proxy. // -// keep-web -listen :9999 -attachment-only-host domain.example:9999 +// "AttachmentOnlyHost":"domain.example:9999" // // Trust All Content mode // -// In "trust all content" mode, Keep-web will accept credentials (API +// In TrustAllContent mode, Keep-web will accept credentials (API // tokens) and serve any collection X at -// "https://collections.example.com/collections/X/path/file.ext". -// This is UNSAFE except in the special case where everyone who is -// able write ANY data to Keep, and every JavaScript and HTML file -// written to Keep, is also trusted to read ALL of the data in Keep. +// "https://collections.example.com/c=X/path/file.ext". This is +// UNSAFE except in the special case where everyone who is able write +// ANY data to Keep, and every JavaScript and HTML file written to +// Keep, is also trusted to read ALL of the data in Keep. // // In such cases you can enable trust-all-content mode. // -// keep-web -listen :9999 -trust-all-content +// "TrustAllContent":true // -// When using trust-all-content mode, the only effect of the -// -attachment-only-host option is to add a "Content-Disposition: +// When TrustAllContent is enabled, the only effect of the +// AttachmentOnlyHost flag is to add a "Content-Disposition: // attachment" header. // -// keep-web -listen :9999 -attachment-only-host domain.example:9999 -trust-all-content +// "AttachmentOnlyHost":"domain.example:9999", +// "TrustAllContent":true +// +// Depending on your site configuration, you might also want to enable +// the "trust all content" setting in Workbench. Normally, Workbench +// avoids redirecting requests to keep-web if they depend on +// TrustAllContent being enabled. +// +// Metrics +// +// Keep-web exposes request metrics in Prometheus text-based format at +// /metrics. The same information is also available as JSON at +// /metrics.json. // package main