Skip to main content

Verify traffic through Balancer

Check both the saved configuration and the response from your site. A successful save does not mean every serving location uses the change.

Verify the request path​

  1. Read your domain configuration:

Use https://<your-api-host> as your API base URL. The host is shown in the Balancer portal. Examples use $BALANCER_API_KEY for an existing credential with the required access.

curl --fail-with-body -sS -X GET "https://<your-api-host>/http-loadbalancers/$HTTP_LB_ID/groups/$GROUP_ID/domains" \
  -H "x-api-key: $BALANCER_API_KEY"

API reference: List domains for an HTTP group

Expect HTTP 200. Check the domain, target values and readiness dates.

  1. Request your site's HTTP endpoint. Replace example.com with your site hostname:
curl -sS -D - -o /tmp/balancer-response http://example.com/

Expect the status and content your application returns, or the redirect or policy response you configured. Compare /tmp/balancer-response with a known application response. A 200 alone does not identify the serving configuration.

  1. For HTTPS, check the presented certificate and response:
curl -v https://example.com/

Expect a successful TLS handshake with the intended site certificate and your expected application response. Check site status codes if the request fails.

  1. Repeat the relevant request after changes. If readback matches but serving behavior differs, contact your NetActuate account manager to check the applied configuration. There is no verified fixed rollout time.

API reference​

Need Help?​

Contact your NetActuate account manager.