Skip to content

Commit

Permalink
fix: clarifying title for gslb section
Browse files Browse the repository at this point in the history
Signed-off-by: Russ Savage <[email protected]>
  • Loading branch information
russorat committed Feb 6, 2024
1 parent 1840d61 commit c9e483f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/network-edge/gslb.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ If an ngrok point of presence fails, health checks automatically detect that
failure and update our DNS resolution such that clients will attempt to connect
to your endpoints via the next-closest healthy point of presence.

### Disabling GSLB {#endpoints-disabling-gslb}
### Disabling GSLB for an Endpoint {#endpoints-disabling-gslb}

There is no way to disable GSLB for HTTPS and TLS endpoints. All endpoints you
create in ngrok are available on ngrok's worldwide global delivery network and
Expand Down Expand Up @@ -161,7 +161,7 @@ agent to simultaneously connect to multiple regions, you must instead run
multiple ngrok agents and [explicitly disable agent
GSLB](#disabling-gslb-agents).

### Disabling GSLB {#agents-disabling-gslb}
### Disabling GSLB in the Agent {#agents-disabling-gslb}

You should always prefer to allow the ngrok agent to use GSLB and connect to
the closest point of presence. However, the ngrok agent does support disabling
Expand Down

0 comments on commit c9e483f

Please sign in to comment.