Overview
The article discusses the transition from using NGINX in Cloudflare's server architecture to a more customized solution. It highlights the evolution of Cloudflare's software stack over six years and the impending change in the HTTP response header from 'Server: cloudflare-nginx' to 'Server: cloudflare'.
What You'll Learn
1
How to recognize the transition from cloudflare-nginx to cloudflare in HTTP responses
2
Why Cloudflare moved away from using NGINX for handling HTTP requests
3
When to update software that relies on the Server header for Cloudflare
Key Questions Answered
Why is Cloudflare transitioning from cloudflare-nginx to cloudflare in HTTP responses?
Cloudflare is transitioning to 'Server: cloudflare' to reflect the significant changes in their software stack and to move away from reliance on NGINX, which has become less central to their architecture. This change is part of a broader strategy to customize their solutions for efficiency and simplicity.
What changes have occurred in Cloudflare's software stack over the years?
Over the past six years, Cloudflare has evolved from a stack primarily using NGINX, PHP, and PowerDNS to a more complex architecture featuring their own DNS server, RRDNS written in Go, and Lua for business logic, along with new technologies like Railgun, Warp, and Argo.
When will the change in the Server header take place?
The transition from 'Server: cloudflare-nginx' to 'Server: cloudflare' will occur in stages between December 18, 2017, and January 15, 2018. During this period, HTTP responses may contain either header.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Backend
Nginx
Used as part of Cloudflare's server architecture for handling HTTP requests.
Backend
Rrdns
Cloudflare's own DNS server, replacing PowerDNS.
Backend
Lua
Used for business logic that was previously handled by PHP.
Backend
Railgun
A technology added to Cloudflare's edge stack.
Backend
Warp
Another technology integrated into Cloudflare's services.
Backend
Argo
Part of the new technologies added to Cloudflare's edge stack.
Key Actionable Insights
1Update your software to recognize the new Server header format from Cloudflare.If your application relies on the Server header to identify Cloudflare, ensure that it can handle the new 'Server: cloudflare' response to avoid any disruptions in service.
2Consider the implications of moving away from established technologies like NGINX.As Cloudflare has shown, transitioning away from widely used software can lead to more tailored solutions. Evaluate whether your current stack meets your needs or if a custom solution could provide better performance.
3Stay informed about changes in the software stack of services you depend on.Being aware of such transitions can help you prepare for necessary updates in your own systems, ensuring compatibility and continued functionality.
Common Pitfalls
1
Failing to update software that relies on the Server header can lead to compatibility issues.
As Cloudflare transitions to a new Server header format, any software that checks for 'cloudflare-nginx' will not function correctly unless updated. It's crucial to stay ahead of such changes to ensure seamless operation.