You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openserverless.apache.org by "sciabarracom (via GitHub)" <gi...@apache.org> on 2025/09/30 16:51:21 UTC
[I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
sciabarracom opened a new issue, #175:
URL: https://github.com/apache/openserverless/issues/175
- [x] I have searched the [issues](https://github.com/apache/openserverless/issues) of this repository and believe that this is not a duplicate.
### Ⅰ. Issue Description
Since we are using the go git library it is supposed it supports the standard environment variables HTTP(S)_PROXY ... but it does not.
### Ⅱ. Describe what happened
seth the variables, and try ops -update... error!
### Ⅲ. Describe what you expected to happen
it should work!
### Ⅳ. How to reproduce it (as minimally and precisely as possible)
set the variables and try it
### Ⅴ. Anything else we need to know?
### Ⅵ. Environment:
- K8S Runtime and version:
- OPS CLI version: 0.1.0-2409121919.dev
- Others:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "sciabarracom (via GitHub)" <gi...@apache.org>.
sciabarracom commented on issue #175:
URL: https://github.com/apache/openserverless/issues/175#issuecomment-6506226239
closing as not replicated
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "ayush00git (via GitHub)" <gi...@apache.org>.
ayush00git commented on issue #175:
URL: https://github.com/apache/openserverless/issues/175#issuecomment-6506032000
Hii @sciabarracom
i tested it and could not reproduce it.
with HTTP_PROXY and HTTPS_PROXY set, both a local devcluster (apihost added to NO_PROXY) and a remote server installed with `ops setup server` work, login, ops ide deploy, env list all worked.
so concluson is, ops honours the proxy variables. and for a local apihost the user only needs to add it to NO_PROXY, which is a standard. nothing to fix, this issue can be closed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "ayush00git (via GitHub)" <gi...@apache.org>.
ayush00git commented on issue #175:
URL: https://github.com/apache/openserverless/issues/175#issuecomment-6424421828
Hii, I tried to reproduce this on the current ops (go-git v5.12.0), and ops -update does honor HTTPS_PROXY:
- HTTPS_PROXY=http://127.0.0.1:9 (dead port): fails with proxyconnect tcp: dial tcp 127.0.0.1:9: connection refused, so the proxy is used.
- With a logging proxy: the clone succeeds and the proxy log shows CONNECT github.com:443
- Full -update including the prerequisite downloads: every host (github.com, release-assets.githubusercontent.com, dl.k8s.io, get.helm.sh, kind.sigs.k8s.io) goes through the proxy.
- Only HTTP_PROXY set: ignored for https URLs, which is standard behaviour.
Your build ([dc51b9](https://github.com/apache/openserverless-cli/commit/dc51b997d2c71274d1bab6f88aae0fe63ce7e145), or https://github.com/apache/openserverless-cli/releases/tag/v0.1.0-2409121919.dev) used the same go-git version and the same clone/pull code. go-git’s default client uses `http.DefaultTransport`, which reads the proxy env vars, so I don’t think this was a regression that got fixed later. I even tried this version of the cli locally and got the same results.
What I could reproduce is a TLS-intercepting proxy whose CA isn’t trusted: it fails with x509: certificate signed by unknown authority, and works with SSL_CERT_FILE=<ca.pem> (Linux only). Most corporate proxies re-sign HTTPS, so this would look like “proxy doesn’t work” even though traffic goes through it.
@sciabarracom, could you share the exact error you got? If it’s an x509 error, the fix would be a CA option rather than proxy support. go-git already exposes `CABundle` and `InsecureSkipTLS` on `CloneOptions`/`PullOptions`, so we could add something like `OPS_CA_BUNDLE` / `OPS_INSECURE_TLS` and pass `--cacert` / `-k` to the prerequisite curl calls.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "sciabarracom (via GitHub)" <gi...@apache.org>.
sciabarracom commented on issue #175:
URL: https://github.com/apache/openserverless/issues/175#issuecomment-6443076745
actually the issue is more subtle than this - try to deply in a local installation of openserverless behing a proxy - you will have to propagate to bun the env vars
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "ayush00git (via GitHub)" <gi...@apache.org>.
ayush00git commented on issue #175:
URL: https://github.com/apache/openserverless/issues/175#issuecomment-6449544989
Thanks for the hint, I reproduced with `ops setup devcluster` behind a proxy (`HTTP_PROXY`/`HTTPS_PROXY` set, `NO_PROXY=localhost,127.0.0.1`, proxy refusing loopback targets like a corporate one does).
The cluster deploys fine, but the final `ops setup openserverless login` loops for 600 s with HTTP status code 502: `wsk` sends `GET http://miniops.me/api/v1/namespaces` to the proxy, which can't reach miniops.me (127.0.0.1). Same for bun, `ops env list` sends its POST req to the proxy and fails with Error while making API request. Adding the `apihost` to the bypass list (NO_PROXY=localhost,127.0.0.1,miniops.me) makes both work immediately.
So the env vars are propagated, `wsk`, bun and curl all honor HTTP(S)_PROXY/NO_PROXY the same way.
the issue is so interesting, the issue is that ops never adds its own apihost to `NO_PROXY`, so requests meant for the local machine go to the proxy. Since ops sets the `apihost`, it should append it to `NO_PROXY` for the processes it spawns.
I'll do the same in my local machine and test it, if it works fine i'll open a PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] ops does not support HTTP_PROXY and HTTPS_PROXY env var [openserverless]
Posted by "sciabarracom (via GitHub)" <gi...@apache.org>.
sciabarracom closed issue #175: ops does not support HTTP_PROXY and HTTPS_PROXY env var
URL: https://github.com/apache/openserverless/issues/175
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org