Same proper re-investigation as freshporno (DevTools + Bright Data residential cross-IP + curl_cffi browser TLS). porn00's final CDN fe.porn00.org/...?token=&expires= is PORTABLE cross-IP (token resolved from one residential IP replays 206 from a different Bright Data residential IP) and only rejects non-browser TLS (plain curl 403, curl_cffi chrome 206). In #20 I tested the final URL with a standalone plain curl, got 403, wrongly concluded "IP-bound" and left it on WebView (and before that it used force_proxy, which violated the no-proxy stance). porn00 flashvars are plain get_file (already decoded, no function/0 prefix), so extend _kvs._URL_RE to match both forms — real_url passes plain URLs through unchanged, _resolve_get_file follows the 302 in-session. porn00.py becomes a thin _kvs wrapper. Verified no regression for the function/0 tubes (yespornvip/pornditt/ freshporno still resolve 3x mp4). Result: porn00 native multi-quality, mobile_direct, zero proxy/WebView. fpoxxx and pornxp were re-tested the same way and ARE genuinely IP-bound (403 from a different residential IP — their token binds to the resolver IP), so they correctly stay on the WebView fallback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| connectors | ||
| extractors | ||
| models | ||
| normalize | ||
| resolve | ||
| scheduler | ||
| templates | ||
| __init__.py | ||
| auth.py | ||
| config.py | ||
| db.py | ||
| ingest.py | ||
| main.py | ||