unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Michael Rohleder" <mike@rohleder.de>
Cc: 45179@debbugs.gnu.org
Subject: bug#45179: qutebrowser stuck at Cloudflare 'browser checks'
Date: Tue, 06 Apr 2021 16:56:08 -0500	[thread overview]
Message-ID: <CAGZ5M6N9UN3.34SCR6C6KEH3I@masaki> (raw)
In-Reply-To: <CAGYUM4RXECK.3RC69VJEKRTBU@masaki>

On Tue Apr 6, 2021 at 4:41 PM CDT, bdju wrote:
> While I was able to bypass the cloudflare checks in IceCat with that
> User Agent Switcher addon, I found I so far haven't been able to get
> past them in qutebrowser by changing my useragent. I tried both your
> example and copying one of the useragents generated by UAS in IceCat.
> Still caught in a loop. (and I am using --temp-basedir as you said, so
> shouldn't be my config)
I was too hasty! I both had to change my useragent and wait a long time!
I didn't measure the time, but I'd guess over 10 minutes for Gitlab to
work. Livechart took even longer. Thanks so much for this workaround.
Oh, and this works without --temp-basedir, by the way. I should be able
to actually use these sites in my normal session now I think!




  reply	other threads:[~2021-04-06 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 14:41 bug#45179: qutebrowser stuck on browser checks forever bdju via Bug reports for GNU Guix
2020-12-22 16:34 ` bug#45179: qutebrowser stuck at Cloudflare 'browser checks' Michael Rohleder
2021-01-23  4:58   ` ben--- via Bug reports for GNU Guix
2021-01-24  0:05     ` Mark H Weaver
2021-02-01 11:58       ` ben--- via Bug reports for GNU Guix
2021-04-06 21:41   ` bdju via Bug reports for GNU Guix
2021-04-06 21:56     ` bdju via Bug reports for GNU Guix [this message]
2021-04-07  9:55       ` Michael Rohleder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGZ5M6N9UN3.34SCR6C6KEH3I@masaki \
    --to=bug-guix@gnu.org \
    --cc=45179@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    --cc=mike@rohleder.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).