I implemented the Optional fix and another fix given by a PR to the file to fix the KeyError issue.
It worked; however, it seems the endpoint from CF for down returns different results that are potentially not helpful for the tool anymore
With some help from Claude, I was able to pin point the issue by looking at the server-timing result from curl -v "https://speed.cloudflare.com/__down?bytes=1000" 2>&1 | grep -i server-timing and looking at just server-timing
$ curl -v "https://speed.cloudflare.com/__down?bytes=1000" 2>&1 | grep -i server-timing
< access-control-expose-headers: server-timing, cf-meta-ip, cf-meta-request-time, cf-meta-colo, cf-meta-asn, cf-meta-country, cf-meta-city, cf-meta-postalCode, cf-meta-latitude, cf-meta-longitude, cf-meta-timezone
< server-timing: cfL4;desc="?proto=TCP&rtt=11315&min_rtt=9187&rtt_var=4965&sent=5&recv=7&lost=0&retrans=0&sent_bytes=2837&recv_bytes=516&delivery_rate=315228&cwnd=52&unsent_bytes=0&cid=788a04b6518262a1&ts=34&x=0"
The result is vastly different than what is expected and may not be completely usable anymore...?
I implemented the
Optionalfix and another fix given by a PR to the file to fix theKeyErrorissue.It worked; however, it seems the endpoint from CF for
downreturns different results that are potentially not helpful for the tool anymoreWith some help from Claude, I was able to pin point the issue by looking at the
server-timingresult fromcurl -v "https://speed.cloudflare.com/__down?bytes=1000" 2>&1 | grep -i server-timingand looking at justserver-timingThe result is vastly different than what is expected and may not be completely usable anymore...?