Alt-Svc: why a connection uses a different endpoint

Core idea

Alt-Svc lets a client use another endpoint for the same origin. It changes the network destination rather than URL authority: certificate checks still apply to the original origin.

For Alt-Svc: why a connection uses a different endpoint, distinguish device, router, proxy endpoint, exit IP, ASN, and geolocation estimate. They describe different points in a network. A database may return a regional center or carrier gateway, so an IP result must never be presented as a person's exact physical address.

What the primary source establishes

Observe an alternative service, its lifetime, and origin identity when the network endpoint changes unexpectedly.

The primary source, RFC 7838 — Alt-Svc, RFC 9110 — Origin, RFC 9114 — HTTP/3, RFC 9000 — QUIC, MDN Alt-Svc, defines the technical baseline but not every client and provider configuration. Read the normative behavior with its version and then verify your implementation. Treat anything beyond the source as a product feature that needs separate confirmation.

Controlled lab

Serve a marker and Alt-Svc pointing to another port with a valid certificate. Repeat in one profile, then break the alternative certificate and close its port. Require safe fallback or an explicit failure, never acceptance of the wrong identity.

Step-by-step verification

Advertise a short-lived alternative on two owned endpoints. Capture the first response, subsequent attempt, negotiated protocol, remote peer, expiry, clearing, and failure behavior.

Draw the client-to-endpoint path and mark DNS, NAT, and proxying. Capture direct and proxied address family, exit IP, ASN, claimed region, and time. Repeat mobile-network runs because carrier gateways may change without physical movement.

Compare product location, actual ASN, and at least two independent databases. City disagreement can fit normal accuracy limits. Verify country before a strict-country session; use device location with explicit permission when a workflow truly needs coordinates.

• Publish a short-lived alternative
• Capture the remote endpoint
• Break alternative identity
• Verify expiry and fallback

Evidence to retain

Record origin URL, Alt-Svc value and age, remote endpoint, ALPN, certificate identity, timestamps, fallback, and profile cache state.

Record a masked IP or internal ID, address family, ASN, organization, network type, database, and update date. Collect evidence in one time window. Do not publish connection credentials or unnecessary coordinates.

Define report columns and time format before the run. A result without context becomes a guess: the address, cache state, and changed condition are unknown. Record controlled failures as well as successes so the check proves that it can distinguish states.

Interpreting the result

A proxy or client may decline the alternative. Diagnostics must keep origin URL distinct from socket peer, DNS, and protocol; another IP is not necessarily an HTTP redirect.

Alt-Svc support and caching are client-specific. Browser behavior does not establish API-library or proxy behavior.

One successful run confirms only one client, route, and moment. Repeat while changing one variable and state the limits. When observation conflicts with documentation, rule out cache, client version, and intermediaries before creating a reproducible support case.

Worked decision process

Draw Alt-Svc: why a connection uses a different endpoint as device, gateway, public NAT, proxy entrance, proxy exit, DNS, and origin, with address family and measurement point. This prevents local addresses from entering remote allowlists and separates entry-server location from exit geography.

Correlate geography with ASN and observation time. Databases age differently, carrier gateways are shared, and anycast changes paths. A city mismatch is not proof of failure; verify country and exit IP in the same session as the application request.

Troubleshoot local DNS and routes, entry connectivity, authentication, exit family, and destination reachability in order. Ping does not test HTTP CONNECT. After a fix, repeat the original small scenario with the same DNS and destination.

Common mistakes

Do not allowlist 192.168.x.x on an external service, confuse CGNAT with a proxy, or treat an ISP label as proof of a mobile device. IPv6 and DNS handling also vary by client, so validate the full path with the actual application.

Stop when errors rise, a source returns a limit, the task would require bypassing protection, or secrets enter logs. Save sanitized diagnostics and correct the cause first. More concurrency or another IP can hide the fault and add load without improving evidence.

Rollout and maintenance criteria

Define the decision boundary before rollout: which observation permits continuation, which requires review, and which stops the workflow. Record acceptable error ratio, maximum wait, and the owner of every exception so a temporary failure cannot silently become permanent configuration.

Review real load, cost, and quality after the first week. Schedule a small control after client, proxy-service, or network changes. Archive outdated instructions with their replacement date and reason so operators do not follow conflicting configurations.

Operational checklist

Turn the successful experiment into a short procedure covering owner, safe configuration, limits, and stop conditions. Every run needs a terminal status. After browser, library, or network changes, run a small control before the main queue.

• Every route address is labeled
• DNS and NAT are separate
• Direct and proxy exits are compared
• Database date is known
• City is not treated as exact
• Client compatibility is verified