mirror of
https://github.com/yogeshojha/rengine.git
synced 2026-10-21 07:41:28 +02:00
Yogesh OjhaandClaude Opus 5
e6f8694c64
The scan context offered Both, HTTPS only and HTTP only. It reached the launch preview, the context diff and the run comparison, where a change raised the comparability verdict, and no stage read it. Picking HTTPS only probed http exactly as before. PROBE_SCHEME turns the setting into the scheme every bare host:port carries, and HttpxClient adds -no-fallback-scheme so httpx does not retry the other one when the named scheme fails. A target that already names a scheme is left alone, so the endpoint probe and the screenshot pass keep working from URLs that answered. Restricting the probe restricts the whole run: the crawler, the fuzzer and the vulnerability surface all read schemes off what http_probe recorded, so nothing further downstream needs a filter of its own. NetOptions loses user_agent, which was derived on every call and read nowhere, and carries probe_scheme in its place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X5roHYDYzSPRNaTkn8hSkJ
The file is empty.