Table of contents

Assets: how they work

This page was imported from the opsmanual on GitHub Enterprise. It hasn’t been reviewed for accuracy yet. View history in old opsmanual

Assets are stylesheets (CSS), JavaScript (JS) and image files which make GOV.UK look the way it does. When we use the term assets we don’t include PDFs and other files which are attached to government publications - we call these attachments.

How users access assets

In production, the GOV.UK content delivery network is in front of our assets hostname.

In other environments there’s no CDN and the assets hostname points directly to our origin servers.

Assets at origin

Assets are served by the cache machines in all environments.

The cache machines proxy requests to the application hostnames based on the first segment of the path. For example /government-frontend/ is proxied to the hostname for government-frontend in that environment.

All other assets that have a path that don’t match fall back to the static application.

This page is owned by #2ndline and needs to be reviewed