From bc5fc5a5131aa8e9befb0cafb93c50e7c67be5f6 Mon Sep 17 00:00:00 2001 From: Brady Mitchell Date: Tue, 13 Aug 2019 09:01:07 -0700 Subject: [PATCH] remove unnecessary tags --- docs/configuration/configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuration/configuration.md b/docs/configuration/configuration.md index 5488d58..a5ef23f 100644 --- a/docs/configuration/configuration.md +++ b/docs/configuration/configuration.md @@ -133,7 +133,7 @@ For example, the `--cookie-secret` flag becomes `OAUTH2_PROXY_COOKIE_SECRET` and the `--set-authorization-header` flag becomes `OAUTH2_PROXY_SET_AUTHORIZATION_HEADER`. -## Logging Configuration +## Logging Configuration By default, OAuth2 Proxy logs all output to stdout. Logging can be configured to output to a rotating log file using the `-logging-filename` command. @@ -231,7 +231,7 @@ Available variables for standard logging: | File | main.go:40 | The file and line number of the logging statement. | | Message | HTTP: listening on 127.0.0.1:4180 | The details of the log statement. | -## Configuring for use with the Nginx `auth_request` directive +## Configuring for use with the Nginx `auth_request` directive The [Nginx `auth_request` directive](http://nginx.org/en/docs/http/ngx_http_auth_request_module.html) allows Nginx to authenticate requests via the oauth2_proxy's `/auth` endpoint, which only returns a 202 Accepted response or a 401 Unauthorized response without proxying the request through. For example: