-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare Passes completely broken #291
Comments
Thank you so much. We are working on it. |
#292 for tracking |
By me had the same issue but seemed to be by me it screwed up the CSS but if used in Incognito it was fine and as soon I disabled the extension (privacy pass) soo don't know if that's related also or just me |
This has been resolved in v3.0.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reason for this seems simple: you (cloudflare) rolled out a new version of the captcha challenge that broke your (privacy pass) extension.
E.g. the extension looks for POSTs with
__cf_chl_captcha_tk__' or '__cf_chl_managed_tk__
to detect a challenge submission (see). But requests with these parameters do not exist anymore. The closest is__cf_chl_rt_tk
, but that one isn't even used in the POST itself, it's just pushed onto the browser history when that challenge js is loaded and replaced again afterwards. The final submission POST cannot be detected that way, and the extension will therefore never even attempt to do an issuance.Tested broken: Firefox and Chrome (no surprise), extension version 3.0.0
The text was updated successfully, but these errors were encountered: