Re: waiting forever for the Cloudflare check

immibis <news@immibis.com> writes:

What if we (and by "we" I mean "whoever is interested, motivated, and
capable of defending themself from copyright lawsuits, so probably not
me") made a specialized outproxy to bypass site-specific garbage?

  It seems that the Cloudflare check sometimes runs into an
  endless loop. If it has not finished after few seconds,
  it is possible that it ran into such a loop.

  I can't remember the details now, but IIRC, sometimes, such
  an endless loop happened when an "http" address was used.
  It did continue, sometimes, after the "http" was replaced by
  "https". This would make some sense since Cloudflare says that
  it is checking that the connection is "secure". However, good
  software of course in such as case would explain to the user
  what's wrong and not just go into an endless loop!

  If there are any MIDM proxies (software which decodes and
  re-encodes TLS data between the browser and the server),
  it might also be worth a try to bypass those proxies.