Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as www. before example.com? I ask this after switching from one CDN (Cloudflare...
#4: Post edited
by
Alexei
·
2021-05-23T08:21:50Z (almost 3 years ago)
added relevant tags
- Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?
I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain;<br>I don't really care from that, it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100 or 1,000 unique IP visits per month, and that's somewhat misses the very purpose of CDNs, so why?
- Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?
- I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain;
- I don't really care about that, it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100 or 1,000 unique IP visits per month, and that's somewhat missing the very purpose of CDNs, so why?
#3: Post edited
- Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?
I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain name ;<br>I don't really care from that but it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100-1,000 people a month, and that's somewhat misses the very purpose of CDNs, so why?
- Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?
- I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain;<br>
- I don't really care from that, it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100 or 1,000 unique IP visits per month, and that's somewhat misses the very purpose of CDNs, so why?
#2: Post edited
Why content delivery networks usually require a www. redirect?
- Why content delivery networks often require a www. redirect?
Why do Content Delivery Networks are developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?- I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain name ;<br>
- I don't really care from that but it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100-1,000 people a month, and that's somewhat misses the very purpose of CDNs, so why?
- Why do Content Delivery Networks are often developed in such a way that they would require adding a Cname value such as `www.` before `example.com`?
- I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain name ;<br>
- I don't really care from that but it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100-1,000 people a month, and that's somewhat misses the very purpose of CDNs, so why?
#1: Initial revision
Why content delivery networks usually require a www. redirect?
Why do Content Delivery Networks are developed in such a way that they would require adding a Cname value such as `www.` before `example.com`? I ask this after switching from one CDN (Cloudflare) to another (Namecheap) and coming across the same pattern of the need to add `www.` before the domain name ;<br> I don't really care from that but it's just that four redirects `http → https → httpsWITHOUTwww → httpsWITHwww` can make websites load somewhat slower, especially on shared hosting environments, even with traffics of 100-1,000 people a month, and that's somewhat misses the very purpose of CDNs, so why?