Just upgraded to Detect CLI 8.x. Now my proxy config is completely ignored. Classic "upgrade."
My pipeline runs in a locked-down VPC, everything routes through a proxy. 7.x worked fine with the standard env vars (`HTTP_PROXY`, `HTTPS_PROXY`, `NO_PROXY`). Now? Total timeout failure.
* Tried the new `--detect.http.proxy.host` and `--detect.http.proxy.port` flags. Nada.
* Their docs are a masterpiece of ambiguity.
* Feels like they abstracted away the basic networking layer for no good reason.
Anyone found a workaround that doesn't involve rewriting the entire CI job or bypassing security? Or do I just roll back to 7.x and wait for 9.x to break something else?
fight me
Yeah, that's a rough spot. The move away from standard env vars has been a pain point for a few folks on our team, too. It seems the CLI now uses its own internal HTTP client that requires those new, explicit flags.
We found you might need to also explicitly set `--detect.http.proxy.username` and `--detect.http.proxy.password` as flags if your proxy needs auth, even if the env vars used to pass them automatically. The docs really don't make that dependency clear.
Rolling back to 7.x is a solid temp fix, honestly. We're logging this with their support as a breaking change for air-gapped environments.
Review first, buy later.
Rolling back is your only viable move right now. The new proxy "features" aren't just poorly documented, they're a deliberate vendor lock-in play. They've broken a universal standard that's worked for decades just to force you onto their proprietary configuration path.
You'll notice they didn't just add new flags as an alternative. They actively removed support for the standard env vars. That's not an accident or an oversight in the code. It's a strategic change to increase control and, I suspect, to later monetize "enterprise proxy management" as an add-on module. Classic vendor playbook.
The temporary fix is to go back to 7.x. The permanent fix is to start evaluating other tools that don't treat basic network connectivity as a premium feature.
Show me the data
Welcome to the "improved" user experience. They broke a fundamental UNIX contract that's been around longer than most of the devs writing the tool.
Rolling back is the correct play. Don't waste a day trying to appease a broken abstraction. Pin your version to `7.x` in your pipeline and add a comment that says "Do not 'upgrade' until they re-implement basic networking."
If your security team squawks, tell them the new version can't reach the outside world at all, which is a bigger problem than running a known, working version.
If it ain't broke, don't 'upgrade' it.