[Bug]: HTTP proxy stopped working

[andibeuge]

Bug Description

With the release 1.4x.x the http proxy connections seem to have stopped working.

The connection can be opened successfully with the hoop cli

--------------------http-connection-------------------
               host=127.0.0.1 port=8081
------------------------------------------------------
ready to accept connections!
{"level":"info","timestamp":"2025-12-09T11:07:43+01:00","logger":"proxy/httpproxy.go:69","msg":"session=108f9d9e-c340-4cc3-806b-a8088e060a89 | conn=1 | client=127.0.0.1:50103 - connected"}

but using this connection

curl -x localhost:8081 https://ifconfig.me

times out:

curl: (28) Proxy CONNECT aborted due to timeout.

The logs the agent indicate that there is something off with assembling the proxy params:

{"level":"info","timestamp":"2025-12-09T10:07:43Z","logger":"httpproxy/proxy.go:107","msg":"http resquest, CONNECT http://egress-proxy.infra.svc.cluster.local:3128ifconfig.me:443, content-length=0, mutate-headers=[]","conn":"1"}

Steps to Reproduce

• create a new http proxy connection
• use a cluster internal proxy service as http proxy (squid or sth)
• try the connection using the hoop cli

Expected Behavior

the local curl command gets routed through the proxy

Actual Behavior

the connection times out in the proprietary httpproxy/proxy.go implementation

Version

1.46.4

Browser(s)

Other

Operating System

macOS

Screenshots

No response

Additional Context

No response

Relevant Log Output

{"level":"info","timestamp":"2025-12-09T10:07:43Z","logger":"httpproxy/proxy.go:107","msg":"http resquest, CONNECT http://egress-proxy.infra.svc.cluster.local:3128ifconfig.me:443, content-length=0, mutate-headers=[]","conn":"1"}

Code of Conduct

• I agree to follow this project's Code of Conduct

[mtmr0x]

hey @andibeuge, it looks like you are trying to use curl to proxy your localhost:8081 to https://ifconfig.me, as per your example. That won't work with Hoop in that way. The target URL you are trying to connect via the proxy should be configured inside hoop. Go to your Resource, edit the role with the information to point to the desired URL and then you can access it directly via localhost:8081.

Let me know how it went.

[andibeuge]

Hey @mtmr0x,

thanks a lot for the clarification - I thought it could be used as a generic proxy. I remember doing tests with socks5 (with v1.39.x I think). This was working actually and therefor I thought it broke.