Dave (SOD)
It is difficult to say how many of the so called bugs are really bugs, or due to CF. This is something we came across.
Once you do something – an action – it is supposed to update something in your account or somewhere on the site. There will be a delay whilst CF checks to see if it is happy with what you did, but because of the delay, the place which is supposed to update failed to do so because of possible time out creating an internal error.
The only way the developers will be able to check if the bugs you report are really bugs is by testing the site (on test site) outside the protection of live site which is currently using CF, to ascertain what is or isn’t a bug.
So it is my belief that if the site developers try to fix the bugs on the CF linked live site, the results will be variable because of the different site connection speeds. It might work for them, but fail for the user and so on.
Ketan at ARC
An interesting point, and quite possible. I’m not party to Morton’s technical solution and can only guess based on previous painful experience.
Website services timing out because of network or security gateway delays could cause the dreaded ‘undefined behaviour’, which often explains why some bugs mysteriously come and go.
I have no experience of Cloudflare other than as a user here. The way it repeatedly asks me to confirm I’m human mid-session is very annoying, not least because it wastes about 20 seconds every time! However, poor performance could be hardware, not enough memory or cpu, or slow IO etc. My money is on software issues – things in the configuration that whack the server, such as wasteful database queries, inadequate buffering, too many bells and whistles, inefficient plug-ins, garbage collection problems, or higher payloads than the designer expected. Time will tell.
Dave