# How does redirect caching work? **URL:** \ **Category:** Support\ **Tags:** redirects\ **Created:** [August 23, 2020, 9:47pm UTC](https://answers.netlify.com/t/how-does-redirect-caching-work/21265 "2020-08-23T21:47:45Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![fool](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/fool/32/37_2.png) [@fool](https://answers.netlify.com/u/fool)\ **Post date:** [August 27, 2020, 7:57pm UTC](https://answers.netlify.com/t/how-does-redirect-caching-work/21265/4 "2020-08-27T19:57:58Z")
I’ve heard “10k redirects can add hundreds of ms”. All cases will differ, so there is no exact metric. As I said, we do some caching, and if you have a redirect like: /blog/\* [https://wpengine.com/:splat](https://wpengine.com/:splat) 301! …that gets cached and requests to /blog/\* will be quick - but that doesn’t affect every other asset like logo.png. It also doesn’t fix the problem to “just cache 301s”, for instance: - we have to check for files that AREN’T covered by a redirect, over and over again. We can’t necessarily cache all your RULES at the CDN edge, when you have this many rules! We want to use the cache for FILES, not rules, so the cache size for files is much larger, and 25k redirects is way more than we want people to have, so we aren’t optimizing for that use case. - Also, we have dozens of CDN nodes and EACH has its own, independent cache, so one node might get everything cached - and the other nodes don’t. If you want to send an x-nf-request-id for a slow request that you’d like me to look into, I’ll be happy to advise if there are any easy wins - sometimes, you just have DNS misconfigured, and it isn’t even about redirects! Talking about this in the abstract isn’t going to help further, I think 🙂 this article describes what I’m looking for: > [@\[Support Guide\] Netlify Support asked for the 'x-nf-request-id' header? What is it and how do I find it?](https://answers.netlify.com/t/support-guide-netlify-support-asked-for-the-x-nf-request-id-header-what-is-it-and-how-do-i-find-it/4385): > > Last reviewed by Netlify Support in July 2025 What is the x-nf-request-id header? Web servers and web browsers communicate using a protocol called HTTP - which stands for “HyperText Transfer Protocol”. Both web browsers and web servers use a feature called headers as part of this protocol. The headers that web browsers send are called “request headers” because the browser in making an “HTTP request”. The web servers headers are called “response headers” because web servers send an “HTTP respo… If you proxy through cloudflare to Netlify, won’t be able to help much further though. Here’s why: > [@\[Support Guide\] What problems could occur when using Cloudflare in front of Netlify?](https://answers.netlify.com/t/support-guide-why-isn-t-my-ssl-certificate-provisioning-automatically-with-cloudflare-netlify-are-there-other-problems-with-using-cloudflare-in-front-of-netlify/138): > > sparkles [AskNetlify’s](https://docs.netlify.com/ask-netlify/) Version sparkles What risks come with proxying to Netlify? Copy the prompt above and paste it into [AskNetlify](https://docs.netlify.com/ask-netlify/), and it’ll break down this info. You can also ask clarifying questions. Still need help? No problem! We’re happy to clarify. Last reviewed by Netlify Support - July 2025 Note: We recommend not using both Cloudflare’s CDN (“Accelerate and Protect”, the orange cloud in their UI) and Netlify for the same site at the same time. Why? Read on! Netlify’s web se… Please make any x-nf-request-id you send is from a direct-to-netlify connection 🙂 --- _[View the full topic](https://answers.netlify.com/t/how-does-redirect-caching-work/21265)._