@SuzanneAldrich Is there an easy way to find out why Cloudflare shows a 520 error for a URL? Thinking HTTP2 push leads to > 8k headers.
-
-
Replying to @csixty4 @SuzanneAldrich
make the same request against the origin is one way to eliminate large headers as a cause: https://support.cloudflare.com/hc/en-us/articles/219304477 …
1 reply 0 retweets 0 likes -
-
Replying to @csixty4 @SuzanneAldrich
the more common scenario is a TCP reset - normally caused by the web server crashing and visible in error logs
1 reply 0 retweets 0 likes -
Replying to @Cloudflare @SuzanneAldrich
I'm not sure a lot of the people reporting these errors are going to be able to troubleshoot something like that
1 reply 0 retweets 0 likes
Replying to @csixty4 @SuzanneAldrich
it's tricky for sure - it's a rare error but out support team can always help pinpoint the root cause for you
8:16 AM - 17 May 2016
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.