-
Notifications
You must be signed in to change notification settings - Fork 0
Two inherited defects: --fingerprint always 400'd, and the shipped credential check was dead #10
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1302,8 +1302,21 @@ def parse_args(): | |
| "API and apply it to the launched browser. Needs " | ||
| "--twocaptcha-key. Ignored with --cdp-endpoint, where the " | ||
| "Scraping Browser supplies its own.") | ||
| p.add_argument("--fp-tags", default="Windows,Chrome,Desktop", | ||
| help="Fingerprint filter tags (default: Windows,Chrome,Desktop)") | ||
| # ONE OS-family tag, not a list — and this default is what makes | ||
| # --fingerprint work at all. It shipped as "Windows,Chrome,Desktop", | ||
| # which the fingerprint API rejects with HTTP 400 ("Request parameters | ||
| # are invalid"), so --fingerprint failed on every invocation. | ||
| # | ||
| # fingerprint_client.py's own --tags help has said so all along; the | ||
| # engines' default contradicted it. Measured against the live API on | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Minor: this claims a fresh measurement "on 2026-09-10," a day after the "Measured 2026-09-09" note already in |
||
| # 2026-09-10: `Windows` succeeds, and `Windows,Chrome,Desktop`, | ||
| # `Chrome` and `Desktop` each 400. | ||
| p.add_argument("--fp-tags", default="Windows", | ||
| help="ONE OS-family tag for the fingerprint filter: " | ||
| "Windows, Microsoft Windows or Android. NOT a list — " | ||
| "Chrome, Desktop and Mobile are each rejected by the " | ||
| "API with 400, and no combination is accepted. Use " | ||
| "--fp-country to narrow further. (default: Windows)") | ||
| p.add_argument("--fp-country", default=None, | ||
| help="Fingerprint country, ISO 3166-1 alpha-2. Match it to " | ||
| "your proxy's exit country — a US fingerprint on a " | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment says these tokens "were missing, which is why
--allfailed on this repo's own main." That's only true for two of them:"login:password@host:port"(matchesproxy_pool.py:95) and"user:secret@"(matchessmoke_test.py:1150).The other five —
"{user}","myuser:s3cr3t@","u:supersecret@","login:supersecret@","u:pass@h1","u:pass@h2"— don't appear anywhere else in the repo (checked with a repo-wide grep, no extension filter). They don't fix any failure here; they just widen the credential-URL allowlist with exemptions nothing currently needs, and the comment's stated justification doesn't hold for them. Given this is "the architecture used across this family of scrapers" (per CHANGELOG), these look copy-pasted from a sibling repo's fixtures without checking whether they're actually needed in this one. Worth trimming to just the two that are load-bearing, or explaining why the rest guard against something not yet in this repo.