Michal Zalecki
Jan 23, 2020 ⋅ 8 min read

Caching headers: A practical guide for frontend developers

Michal Zalecki Senior Engineer at @Tooploox 💎, smart contracts, fan of hackathons, React Wrocław meetup organizer.

Recent posts:

Developing Web Extensions With Wxt

Developing web extensions with the WXT library

Browser extensions are an important part of the web ecosystem. They make our lives easier and enhance our web browsing […]

Debjyoti Banerjee
May 24, 2024 ⋅ 8 min read
Bulma Css Adoption Guide: Overview, Examples, And Alternatives

Bulma CSS adoption guide: Overview, examples, and alternatives

Explore how Bulma CSS simplifies frontend development with its ease of use and customizable, responsive, pre-designed UI elements.

Timonwa Akintokun
May 23, 2024 ⋅ 10 min read
Using Mountaineer To Develop A React App With Python

Using Mountaineer to develop a React app with Python

Develop a React app with Python using the Mountaineer framework for building a simple app with integrated your frontend and backend database.

Rosario De Chiara
May 23, 2024 ⋅ 7 min read
Enhance CSS View Transitions With Velevette

Enhance CSS view transitions with Velvette

Velvette is a utility library developed to make working with view transitions easier.

David Omotayo
May 22, 2024 ⋅ 9 min read
View all posts

3 Replies to "Caching headers: A practical guide for frontend developers"

  1. This is amazing and so valuable. Been looking for something like this to properly setup my headers. Thanks for the write up.

  2. Hi Team,

    I have added below code for caching but it’s not working, please suggest.

    location ~* \.(jpg|jpeg|gif|png|ico|cur|gz|svg|svgz|mp4|ogg|ogv|webm|htc|svg|woff|woff2|ttf)\$ {
    etag on;
    if_modified_since exact;
    expires 30d;
    #add_header Pragma “public”;
    add_header Cache-Control “public, no-transform”;


  3. For SPA html – is it enough to use meta tag headers to tell the browser not to cache? Are they reliable? Or I must setup response headers on the server?

Leave a Reply