Astro Image Component Cache‑Control Header Limits

Cache‑Control header limits for Astro <Image> component across adapters

0 reputation · 01 Nov 2022, 18:53 UTC

50.4K views0

The goal is to determine whether the Astro component should automatically include a sensible Cache‑Control header for optimized images to provide consistent caching behavior without requiring adapter‑specific configuration.

Currently the component does not inject any header by default, and while the Node adapter allows manual middleware to set headers, the Vercel and Netlify adapters rely on their edge caches, leading to inconsistent behavior across platforms.

Should the component emit a default Cache‑Control header? If so, what value (e.g., stale‑while‑revalidate) would be appropriate? How would this default interact with existing adapter‑specific middleware or edge cache settings?

2,254 following

Keep exploring this topic

Nested component hydration order with mixed client directives

When a parent island uses client:visible and a nested child uses client:load, Astro's documentation does not specify which component hydrates first or whether the parent's visibility gate blocks the child. This affects LCP and layout shift.

Astro hydration mismatch behavior when switching output modes from static to server

Investigating how Astro handles component hydration mismatches when switching from static site generation to server-side rendering, and whether the framework isolates failing components or provides fallback options.

Content collection validation warnings exit zero in CI despite validate: 'warn'

Astro's validate: 'warn' for content collections exits 0, letting schema violations pass CI. No structured diagnostics or stable warning codes exist to filter and fail selectively.

Astro Middleware vs. Adapter Static Asset Serving: Auth Bypass Risk in Hybrid Rendering

Astro middleware runs on every request in the Node adapter but may be skipped for static assets on edge platforms. Prerendered pages and public/ files bypass middleware entirely, creating auth gaps. No framework API exists to reliably distinguish route types at build time.

Cache‑Control header limits for Astro <Image> component across adapters

0 answers

Your perspective belongs here.

0 question comments