Skip to content

Update Backend.mdx #1460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pablodelolmo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Backend.mdx #1460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions documentation/docs/backend/Backend/Backend.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,18 @@ This includes all configuration options above except for `name`, `target`, `host

A new `Backend` object.

### Disable TLS verification

TLS certificate verification for a backend can be disabled by leaving the following fields **unset** in your `backendConfiguration`:

- `sniHostname`
- `caCertificate`
- `certificateHostname`

If these fields are not configured, the Compute app does not validate the certificate presented by the backend. As a result, it will accept certificates that are expired, self-signed, issued for a different hostname or otherwise invalid.

However, as a best practice, your origin should serve a valid TLS certificate and your Compute app should verify it to help protect backend connections from man-in-the-middle attacks.

## Examples

In this example an explicit Dynamic Backend is created and supplied to the fetch request, the response is then returned to the client.
Expand Down
Loading