Delivery and origin configuration basics

01 / Getting started

Prepare the delivery profile

A delivery profile begins with a public hostname, a defined content source and a clear policy for freshness and origin access. Before activation, verify that the source returns the intended content type, status code and cache metadata.

1. Identify the public hostname used for content delivery.
2. Define the authoritative source for each content path.
3. Confirm secure origin connectivity and hostname validation.
4. Set explicit cache headers for reusable assets.
5. Validate representative files before wider use.

02 / Cache behavior

Use explicit response metadata

Cache behavior is most predictable when the origin provides explicit freshness information. Where supported by the profile, standard cache directives can be used to define whether a response is reusable and how long it remains fresh.

Assets with versioned filenames can generally use longer freshness periods than mutable files. Sensitive or user-specific responses should not be treated as shared static content.

03 / Object storage

Keep object names stable and descriptive

Object collections should use consistent path conventions and correct content types. Avoid changing the contents of a long-lived object path without also reviewing cache behavior.

• Use normalized, case-consistent object names.
• Set a correct media type for every object.
• Preserve file extensions where they clarify content handling.
• Use versioned paths for release artifacts and immutable assets.

04 / Origin connectivity

Maintain a clear origin contract

The source should respond consistently for the hostname and path expected by the delivery profile. Secure origins should present a valid certificate for the configured hostname. Redirect behavior, request headers and error responses should be reviewed before activation.

Recommended checks

• The intended hostname reaches the correct source.
• Secure connections complete with valid hostname verification.
• Representative content returns the expected status and media type.
• Error responses do not reveal private application details.

05 / Health checks

Interpret reachability separately from application health

A health check confirms that a selected source path responds under the configured conditions. It does not prove that every application function is correct. Choose a stable path that is inexpensive to serve and representative of source reachability.

06 / Static content

Optimize for predictable retrieval

Static assets should be small enough for practical delivery, use accurate content types and avoid unnecessary variation. Compression, file naming and freshness policy should be decided at the publishing stage.

• Use immutable filenames for versioned application assets.
• Remove development files and source maps unless intentionally published.
• Set download behavior explicitly for files intended as attachments.
• Review large objects for appropriate delivery and update patterns.

For profile-specific questions, contact support@astracloudbox.online.