Introduction: Yesterday bitshares.org was failing to load properly during some hours. That happened as result of a live testing of php /w cdn version of bitshares.org website in order to hit highest score in metrics.
Result: CDN test - failed.
Reason: bitshares.org domain is currently using CloudFlare DNS. By doing so, it falls under the constant pressure of enforced cookies by DNS, very strict and legal ones that doesn't require user to accept them, but when it comes to some metrics in SEO and Optimizations (such as YSlow!), bitshares.org fails to deliver content/media from proper cookie-less domain even if serving them over CDN.
Cons: Different to WordPress, where different plugins and rules of structure of it (wp-content folder being defined by default as cookie-less), and where we were able to deploy CDN and enforce stripdown of cookies served by news.bitshares.org or cdn.bitshares.org, resulting in top scores on metrics. Unfortunately, php/html static websites have no such option.
Solution: Currently bitshares.org worker is prepaid to StackPath and has more budget left in it to serve properly requests coming from news.bitshares.org.
We leave news.bitshares.org using StackPath CDN.
We purchase subscription for KeyCDN who offers in panel "Strip Cookies" and ignores what origin says.
We setup/configure KeyCDN to serve for bitshares.org origin all the content from edge.bitshares.org CDN powered origin.
We re-test ready php /w CDN version of bitshares.org
Estimate: 3 hours with testing.
P.S. Since yesterday I've logged nearly 4 hours on entire mess already, trying to push origin that is being ignored by DNS, I believe that this task will be deployed/done without any additional hours logged/submitted to the worker.
Introduction: Yesterday bitshares.org was failing to load properly during some hours. That happened as result of a live testing of php /w cdn version of bitshares.org website in order to hit highest score in metrics.
Result: CDN test - failed.
Reason: bitshares.org domain is currently using CloudFlare DNS. By doing so, it falls under the constant pressure of enforced cookies by DNS, very strict and legal ones that doesn't require user to accept them, but when it comes to some metrics in SEO and Optimizations (such as YSlow!), bitshares.org fails to deliver content/media from proper cookie-less domain even if serving them over CDN.
Cons: Different to WordPress, where different plugins and rules of structure of it (wp-content folder being defined by default as cookie-less), and where we were able to deploy CDN and enforce stripdown of cookies served by news.bitshares.org or cdn.bitshares.org, resulting in top scores on metrics. Unfortunately, php/html static websites have no such option.
Solution: Currently bitshares.org worker is prepaid to StackPath and has more budget left in it to serve properly requests coming from news.bitshares.org.
Estimate: 3 hours with testing.
P.S. Since yesterday I've logged nearly 4 hours on entire mess already, trying to push origin that is being ignored by DNS, I believe that this task will be deployed/done without any additional hours logged/submitted to the worker.
Chee®s