A follow-up to v1.1.0, from the same field report.
LAN cameras are no longer sent through a proxy. A camera on a private address can't be reached through an egress proxy, but snap.sh was still routing to it. snap.sh now passes --noproxy <camera-host> whenever the camera is on a private address. Public hosts keep using the proxy, since for them it may be the only route out.
Relying on no_proxy was not enough, and this is the part worth knowing if you automate anything against a LAN device: CIDR matching in no_proxy only landed in curl 7.86. Older builds ignore no_proxy=192.168.0.0/16 silently — no warning, the request just goes to the proxy anyway. The explicit --noproxy flag works on every version regardless of spelling.
Verified against a real LAN address rather than a loopback fixture, because curl never proxies loopback — a localhost test would have passed either way and proved nothing.
This fixes the common corporate-proxy case. It does not help if your session has no route to the LAN at all (some cloud/bridged setups); nothing in a shell script can fix that, and the README covers the browser workaround for it.
Full changelog: v1.1.0...v1.1.1