CDN for web applications
The app origin should see users, not every CSS file.
SaaS and internal web apps still ship large front-end bundles and public marketing shells from the same origin that runs the application.
Cache hashed front-end assets and anonymous shells at Cloud CDN. Bypass session HTML, authenticated APIs and WebSockets. Use Origin Shield on HTML misses.
Why teams use Aptranet
What CDN for web applications looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Front-end bundles at the edge
JS, CSS and fonts load from 210+ PoPs with HTTP/3.
Session traffic stays on the app
Dashboards and authenticated APIs are not served from cache.
TLS and DDoS on the app hostname
The public name terminates at Cloud CDN with L3-L7 mitigation.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Front the application hostname
Pull the existing app origin over HTTPS.
- 2Cache hashed assets
Long TTL for fingerprinted files. Purge the HTML shell on deploy.
- 3Bypass session routes
Authenticated HTML, APIs and WebSockets go to origin.
- 4Cut over DNS when ready
Validate on an Aptranet hostname first, including login.
Outcomes
What changes once the hostname is on Aptranet.
- App assets are global
- Login and dashboards remain dynamic
- Deploys purge the HTML shell
- The app origin is less exposed
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Only if it is identical for every user, which is rare. Most application HTML should bypass cache.
Yes. See CDN for SPAs, React, Angular and Vue.
Do not cache HTML that embeds per-user CSRF tokens. Static assets can still be cached.
Yes. Cloud CDN supports custom IP and ASN (BYOIP).