Public endpoints
- An endpoint gives a service a public address of the form https://<name>.app.acdn.uz. The name is generated: it cannot be chosen, and it stays the same for as long as the endpoint exists. For a chosen name or your own domain see Custom domains below.
- TLS is terminated by ACDN with a valid certificate for the hostname. Clients may use HTTP/1.1 or HTTP/2; your container receives plain HTTP/1.1 on the port of the endpoint.
- Requests to http:// are answered with a 301 redirect to https://.
- A service can have several endpoints, one per container port. Only HTTP is routed: raw TCP and UDP ports cannot be published.
- An endpoint works while the service has an active release. While the service is stopped, is being replaced during a release with volumes, or has never been deployed, the endpoint answers with an error status such as 503.
- Requests are spread across the instances of the service without session affinity. Keep session state outside a single instance.
- Requests with a header name that contains an underscore are rejected with status 400.
Custom domains
To serve a service on your own domain, or on a name you choose under vvvv.uz, put a CDN pull zone in front of its endpoint. The pull zone provides the hostnames and their TLS certificates and passes every request to the service. A CNAME from your domain straight to the generated app.acdn.uz hostname does not work.
# 1. bind a pull zone to the endpoint; the service then answers at chat.vvvv.uz
python3 acdn-agent.py call /api/user/pull-zones -- --json '{
"name": "chat",
"source_type": "deploy",
"source_deploy_endpoint_id": "ENDPOINT_ID",
"tier": "std"
}'
# 2. add your own hostname; the response contains cname_target
python3 acdn-agent.py call /api/user/pull-zones/hostnames/PULL_ZONE_ID -- \
--json '{"hostname":"chat.example.com"}'
# 3. create the DNS record: chat.example.com CNAME chat.vvvv.uz
# 4. request the certificate, then poll until "status":"active"
python3 acdn-agent.py call /api/user/pull-zones/hostnames/check/PULL_ZONE_ID -- \
--json '{"hostname":"chat.example.com"}'
python3 acdn-agent.py call '/api/user/pull-zones/hostnames/status/PULL_ZONE_ID?hostname=chat.example.com'
- ENDPOINT_ID is the id of the service endpoint, returned in endpoints of the service and application responses. Creating a pull zone needs a verified email address and a balance above zero.
- A pull zone bound to a service supports CORS, Edge Rules, POST and root-path restrictions, uploads and WebSocket. These settings apply only to CDN hostnames; the generated endpoint remains directly accessible. Token Auth and Origin Shield are unavailable. Host, Connection and Upgrade cannot be overridden in Edge Rules; Host and TLS SNI remain the endpoint hostname even when a rule overrides the origin URL.
- Deploy has no default cache lifetime: the application controls caching with Cache-Control or Expires. For public content, return Cache-Control: public, max-age=3600. Without a cache lifetime, responses are not cached; private/no-store and Set-Cookie responses are excluded. Requests with Cookie, Authorization or WebSocket Upgrade bypass the cache. Query-key sorting, coalescing and large-file slicing are available in CDN settings. Cache-key sorting does not reorder the query sent to the application.
- Use a CNAME for a subdomain. For a root domain, host the zone in ACDN DNS; the record is then managed automatically.
- The service receives the generated endpoint hostname in Host. The hostname the visitor used is in X-Forwarded-Host.
- Requests arrive through two proxies, so the visitor address is in a different position of X-Forwarded-For (see Client address).
- HTTP is not redirected to HTTPS on pull zone hostnames by default. Enable the redirect for each hostname with the force-ssl operation; do not rely on X-Forwarded-Proto to detect plain HTTP.
- Request bodies up to 100 MiB are accepted through a pull zone. Requests for well-known sensitive paths such as /.env and /.git are rejected with status 403 before they reach the service.
- The 5-minute WebSocket idle limit and the 15-second response limit apply unchanged.
- Traffic through a pull zone is billed twice: as CDN delivery at the price of the pull zone tier, and as outgoing traffic of the service.
- The generated endpoint hostname keeps working. Deleting an endpoint, its service, or its application also permanently deletes the CDN pull zones linked to the deleted endpoints, including custom hostname settings and ACDN-managed DNS records. The dashboard warns before deletion; the API performs the cascade without an extra confirmation parameter. Remove DNS records at external providers separately.
WebSocket and timeouts
- WebSocket is supported on every endpoint, on the same port as HTTP, with no setting. Connect with wss:// and the endpoint hostname.
- A WebSocket connection is closed after 5 minutes without data in either direction. WebSocket ping and pong frames count as data. Send a ping or an application heartbeat at least once a minute.
- An active WebSocket connection has no maximum lifetime, but it ends when its instance is replaced.
- An ordinary HTTP response must be complete within 15 seconds after the request has been received in full. Otherwise the request is cut off, with status 504 if the response had not started.
- The 15 seconds also apply to streaming responses such as Server-Sent Events and long polling, and to downloads that take longer. Use WebSocket for long-lived connections, and ACDN Storage or CDN for large files.
- The time a client needs to upload a request body does not count toward the 15 seconds.
- During a release, open connections to an old instance end when it shuts down. Clients must reconnect.
Client address
- Your container sees connections from the ACDN gateway, not from the visitor. The visitor's address is passed in the X-Forwarded-For header.
- On the generated endpoint hostname there is exactly one proxy hop. The gateway appends the address of the connecting client as the last value of X-Forwarded-For on every request, including the WebSocket upgrade request. Values before it were sent by the client itself and must not be trusted.
- For rate limiting by IP, use the last value of X-Forwarded-For. In frameworks with a trusted-proxy setting, trust one hop.
- Through a pull zone (custom domain) there are two hops: the last value is an ACDN edge address and the visitor is the value before it.
- A client that calls the generated hostname directly can put its own values in front, so the value before the last one is trustworthy only for requests that really came through the pull zone. To protect a custom domain from abuse, prefer the per-IP request and connection limits of the pull zone, which are enforced at the edge on the real visitor address.
- X-Forwarded-Proto is https for forwarded requests, X-Request-Id carries a unique id for each request, and Host is the endpoint hostname.
Private network between services
- Services of one application reach each other by service name, for example http://api:8080. No endpoint is needed for this.
- A service is reachable by name on its http_port and on the ports of its endpoints. To make a non-HTTP service such as a database reachable, set http_port to its port and leave health_check_path empty; the health check then only tests that the port accepts connections.
- Services of different applications cannot reach each other except through public endpoints.
- Nothing except public endpoints is reachable from the Internet.
Outbound access
- Containers can open outbound connections to public Internet addresses on TCP ports 80 and 443 only, plus DNS.
- All other outbound ports are blocked. This includes SMTP (25, 465, 587), databases and caches on their native ports, SSH, and any UDP service.
- Send email through the HTTPS API of an email provider, and reach external services over HTTPS.
- Private and link-local address ranges are not reachable. ACDN Storage is reachable at https://storage.acdn.uz.
- Outbound connections use shared ACDN addresses; a fixed or dedicated source address is not available.
- Outgoing traffic is limited to 1 Gbit/s per instance and billed per GiB.
Exact request and response fields, limits, and error responses are in the Management API reference.