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
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Why content delivery networks often require a www. redirect?

+2
−0

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 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?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.

+2
−0

Rather than re-iterate all of its points, I will link Netlify's reasoning in To WWW or Not WWW . It's a very eloquent article.

That said, I'll try to summarize in my own words:

  • You need to use a CNAME record to direct traffic to their address name for your webapp. Otherwise it can't serve customers content from a local-to-them server address.

  • You don't want to use a CNAME record on your apex (subdomain-less) domain, because that will prohibit any other records from being registered on your apex domain such as the MX record for email.

  • It doesn't need to be www specifically. That is just a common convention understood by everyone as synonymous with the "root" website.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+3
−1

Other than their preferred configuration options, nothing really "requires" that a particular resource be behind a particular subdomain. Content Delivery Networks (CDNs) are often just setup as separate sites (e.g., a CDN for example.org could be hosted at examplecdn.org or cdn.example.org, etc.)

In most cases, it's just a convention based on best-practices in order to simplify system administration for the back-end IT staff.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »