The API route example used `error_page 401 =401;`, but nginx parses the `=401` as the error_page URI, so an unauthenticated API call is internally redirected to a location named /=401 instead of returning 401 to the client. Drop the directive: without an error_page for 401, nginx returns the 401 from auth_request to the client unchanged. Also add a note that the browser and API snippets show only the routing difference and the rest of the auth_request config (the auth_request_set / proxy_set_header lines that pass X-User, X-Email, token and cookies) must be replicated from the main example. Fixes #3467. Signed-off-by: Mateen Anjum <mateenali66@gmail.com> |
||
|---|---|---|
| .. | ||
| docs | ||
| src/css | ||
| static | ||
| versioned_docs | ||
| versioned_sidebars | ||
| .gitignore | ||
| README.md | ||
| babel.config.js | ||
| docusaurus.config.js | ||
| package.json | ||
| sidebars.js | ||
| versions.json | ||
README.md
Website
This website is built using Docusaurus 2, a modern static website generator.
Installation
npm install
Local Development
npm start
This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.
Build
npm run build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
GIT_USER=<Your GitHub username> USE_SSH=true npm deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.