20 Mar 2012, 11:22 pm
sliqua-jcooter
Veteran
Joined: 25 Jan 2010
Age: 38
Gender: Male
Posts: 1,488
Location: Burke, Virginia, USA
20 Mar 2012, 11:47 pm
nat4200 wrote:
Not posting to argue (I still disagree with the above), but I'm assuming that Cloudflare can't interpret error pages served with a 200 status, and so will not served a cached page when the server hits the too much traffic condition and starts serving "Wrong Planet is currently experiencing a VERY high amount of people posting messages to the site and can't handle the load... We should be back in 1 to 2 minutes or less...To pass the time, watch autism talk tv: ..." for every request.
I point this out because I assume it is contrary to the intended behaviour.
I point this out because I assume it is contrary to the intended behaviour.
Cloudflare's intended function is to mirror exactly what's on display from the main server, irrespective to anything about what it's actually mirroring. Having it displayed as a 500 error wouldn't do anything to change that, nor would that behavior be desirable for a variety of reasons.
EDIT: I don't really care about that discussion either, the primary reason I jumped into the thread to begin with was to address your other two points, which nobody seemed to have any dispute with. I'll just take solace in knowing that I'm right.
20 Mar 2012, 11:56 pm
sliqua-jcooter
Veteran
Joined: 25 Jan 2010
Age: 38
Gender: Male
Posts: 1,488
Location: Burke, Virginia, USA
21 Mar 2012, 12:01 am
nat4200 wrote:
sliqua-jcooter wrote:
nat4200 wrote:
Not posting to argue (I still disagree with the above), but I'm assuming that Cloudflare can't interpret error pages served with a 200 status, and so will not served a cached page when the server hits the too much traffic condition and starts serving "Wrong Planet is currently experiencing a VERY high amount of people posting messages to the site and can't handle the load... We should be back in 1 to 2 minutes or less...To pass the time, watch autism talk tv: ..." for every request.
I point this out because I assume it is contrary to the intended behaviour.
I point this out because I assume it is contrary to the intended behaviour.
Cloudflare's intended function is to mirror exactly what's on display from the main server, irrespective to anything about what it's actually mirroring. Having it displayed as a 500 error wouldn't do anything to change that, nor would that behavior be desirable for a variety of reasons.
EDIT: I don't really care about that discussion either, the primary reason I jumped into the thread to begin with was to address your other two points, which nobody seemed to have any dispute with. I'll just take solace in knowing that I'm right.
Erm, I figured that Cloudflare would serve a cached copy of a page when it gets a 503 error - not as good as a live page but usable
Another one of those things that makes perfect sense from a user perspective, but is in actuality a "Really Bad Idea"(TM).
If the cache layer has criteria for ignoring the output of the origin web server, it makes troubleshooting stale cache issues immensely more difficult. Especially when we as the hosting provider don't have access to the cache layer to look at logs. There are also web servers out there that misuse error codes and report 500 error codes instead of 404 or other more "normal" error codes.
The only instance where cloudflare will/should deviate from the output of the web server is when the server isn't responding at all (ie when the cache gets a TCP reset or TCP timeout, etc).
