Cache-Control Header Generator
Ek correct HTTP Cache-Control response header banayein simple toggles aur human time units se, seedhe aapke browser mein.
Aapka Cache-Control header locally aapke browser mein aapke chune options se assemble hota hai, aur jo aap configure karte hain woh kuch bhi upload ya server par store nahi hota.
Server wire up kar rahe hain? nginx Config Generator try karein.
Cache-Control Header Generator ke baare mein
Yeh cache-control header generator HTTP caching directives ke confusing set ko chand simple toggles mein badal deta hai. public ya private, no-store, no-cache, must-revalidate, proxy-revalidate ya immutable flip karein, aur max-age, s-maxage, stale-while-revalidate aur stale-if-error jaise lifetimes hours, days ya years jaise human units mein set karein bajaye seconds ginne ke. Jaise aap options badalte hain, tool directives ko canonical order mein compose karta hai, plain English mein exactly samjhata hai ki current header kya karta hai, aur no-store ke saath max-age jaise contradictory combinations flag karta hai. Presets rozmarra ke cases cover karte hain: ek one-year immutable static asset, always-revalidate HTML, never-store private data, aur ek split CDN-versus-browser policy. Raw header ya ready-made nginx, Apache aur HTML meta snippets copy karein. Sab kuch aapke device par, browser mein chalta hai.
Features
- public, private, no-store, no-cache, must-revalidate, proxy-revalidate aur immutable ke liye toggles
- max-age, s-maxage, stale-while-revalidate aur stale-if-error ke liye human time inputs (seconds se years)
- Jaise aap edit karte hain, directives ko ek clean canonical order mein compose karta hai
- Current header exactly kya karta hai, iski plain-English explanation
- Mutual-exclusion rules enforce karta hai aur contradictory combinations ke baare mein warn karta hai
- Static assets, always-revalidate HTML, private data aur split CDN/browser caching ke liye one-click presets
- Raw header, nginx add_header, Apache Header set aur ek HTML meta tag ke liye copy-ready snippets
- Poori tarah aapke browser mein chalta hai, isliye jo aap configure karte hain woh device se bahar nahi jaata
Cache-Control Header Generator kaise use karein
- Ek preset chunein ya scratch se shuru karein aur public ya private choose karein.
- Jo directives chahiye toggle karein, jaise no-cache, must-revalidate ya immutable.
- max-age jaise lifetimes ek number aur ek unit (hours, days, years) se enter karein.
- Generated header value aur uske neeche ki plain-English explanation padhein.
- Jo chahiye woh raw header ya nginx, Apache ya HTML meta snippet copy karein.
Example
Input
public + immutable + max-age = 1 year
Output
Cache-Control: public, max-age=31536000, immutable
Classic fingerprinted static-asset policy: ek saal ke liye cache karein aur kabhi revalidate na karein.
Common errors aur troubleshooting
- Aapne no-store set kiya par max-age ya immutable bhi add kiya aur woh gayab ho gaye. — no-store ka matlab kuch bhi kabhi cache nahi hota, isliye woh har doosre directive ko override karta hai. Agar aap sach mein cached-but-controlled response chahte hain to no-store off karein.
- immutable ka koi effect nahi dikhta. — immutable tabhi matter karta hai jab ek response abhi bhi fresh ho, isliye use ek non-zero max-age ke saath pair karein. Bina max-age ke uske apply hone ke liye koi fresh window hi nahi hoti.
- Header private hone par aapka CDN s-maxage ignore karta hai. — private shared caches ko response store karne se bilkul rokta hai, isliye s-maxage, jo sirf shared caches ko target karta hai, kabhi apply nahi hota. Agar CDN ko cache karana hai to public use karein.
- no-cache ek long max-age ke saath aisa behave karta hai jaise cached hi nahi. — no-cache har reuse se pehle origin ke saath revalidation force karta hai, jo effectively us freshness ko cancel kar deta hai jo max-age deta hai. Apne goal ke hisaab se dono mein se ek drop karein.
Aksar pooche jaane wale sawaal
- no-cache aur no-store mein kya difference hai?
- no-store ka matlab response kabhi kisi cache mein likha nahi jaana chahiye, isliye har request wapas origin par jaati hai. no-cache response store karne deta hai, par cache ko use dobara serve karne se pehle origin ke saath revalidate karna hoga. no-store copy na rakhne ke baare mein hai; no-cache hamesha check karne ke baare mein hai ki rakhi copy abhi bhi current hai.
- Cache-Control header mein immutable kya karta hai?
- immutable browser ko batata hai ki resource apne max-age ki lifetime mein kabhi nahi badlega, isliye woh reload par bhi revalidation skip kar sakta hai. Yeh app.9f2c.js jaise versioned ya fingerprinted files ke liye hai, jahan naya build purani ko overwrite karne ke bajaye naye URL par ship hota hai.
- max-age aur s-maxage kaise differ karte hain?
- max-age set karta hai response kisi bhi cache mein, including browser, kitni der fresh rehta hai. s-maxage max-age ko override karta hai par sirf shared caches jaise CDNs aur proxies ke liye. Dono set karne se aap response ko browsers mein thodi der cache karke apne CDN par zyada der rakh sakte hain.
- public ya private kab use karun?
- public shared caches jaise CDNs aur proxies ko browser ke saath response store karne deta hai. private storage ko individual user ke browser tak restrict karta hai, jo personalized ya authenticated responses ke liye sahi choice hai jo shared cache se kisi doosre user ko serve nahi hone chahiye.
- stale-while-revalidate kya karta hai?
- stale-while-revalidate ek cache ko thoda stale response turant serve karne deta hai jabki woh background mein ek fresh copy fetch karta hai. Users ko instant response milta hai aur cache agli request ke liye khud ko update kar leta hai, jo resource expire hone ke moment ko smooth kar deta hai.
- Kya meri configuration server par bheji jaati hai?
- Nahi. Header, explanation aur snippets sab aapke browser mein assemble hote hain jaise aap options toggle karte hain, isliye configuration locally aapke device par process hoti hai aur kuch upload nahi hota.
Related tools
Saare ArrayKit tools