Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs

Dashboard
Notifications
Mark all as read
Q&A

Post History

66%
+2 −0
Q&A Why content delivery networks often require a www. redirect?

2 answers  ·  posted 8mo ago by JohnDoea‭  ·  last activity 7mo ago by corporat‭

Question web cdn redirect
#4: Post edited by user avatar Alexei‭ · 2021-05-23T08:21:50Z (8 months 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 by user avatar JohnDoea‭ · 2021-05-19T13:10:10Z (8 months ago)
  • 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 by user avatar JohnDoea‭ · 2021-05-19T11:26:58Z (8 months ago)
  • 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 by user avatar JohnDoea‭ · 2021-05-19T11:26:02Z (8 months ago)
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?
cdn