feat: SEINT-275 Add http headers default cache-control to public, max-age=3600

[VLegakis]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
walrus-sites-sp	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 0:47am
walrus-sites-sp-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 0:47am
walrus-sites-sw	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 0:47am
walrus-sites-sw-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 0:47am

[codspeed-hq]

CodSpeed Performance Report

Merging #333 will not alter performance

_{Comparing vl/SEINT-275-caching (a2bf444) with main (cae751f)}

Summary

✅ 3 untouched benchmarks

[VLegakis]

After discussion with @Tzal3x we decided to leave this default cache-control policy for the future. Lets leave this PR open-pending and we decide depending on the type of sites being published.

[Tzal3x]

@VLegakis, for now we decided not to include defaults, because we would like to align with current developer common practices.

Take as an example vercel deployments where caching headers are not added to the responses by default.

Implicit/default caching can still be added on the portal level by defining them on next.config.js, without touching the site-builder. But this is something to be taken into account in another phase.

Closing this PR as it's no longer relevant. Thank you regardless! 🙇‍♂️