zeekayandHanzo Dev 7b720f2d37 ingest: connect directly, and cap a fetch the caller did not ...

The guarded client took its proxy from the environment. Through a proxy the
socket the address rules check is the proxy's, so HTTPS_PROXY in the
environment quietly turned the socket-level check off. Both clients this
package builds now dial the target themselves and never use a proxy; a host
that fetches through its own egress injects Web.Client, which is used as given
while Web still applies the pre-flight check, the timeout and the size cap.

Max zero meant no limit, so a server decided how much memory a fetch took.
It now means 32 MiB, and a caller that expects more says so.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-22 23:48:24 -07:00

..

decode.go

ingest: keep binary sources as the bytes they were

2026-09-22 23:47:36 -07:00

file.go

ingest: keep binary sources as the bytes they were

2026-09-22 23:47:36 -07:00

ingest_test.go

ingest: connect directly, and cap a fetch the caller did not

2026-09-22 23:48:24 -07:00

ingest.go

ingest: keep binary sources as the bytes they were

2026-09-22 23:47:36 -07:00

registry.go

semantic: the pipeline, end to end

2026-09-08 12:57:59 -07:00

web.go

ingest: connect directly, and cap a fetch the caller did not

2026-09-22 23:48:24 -07:00