curl
兩個指令，而兩者之間的差異就是全部的價值所在。
curl-host
Section titled “curl-host”在主機網路命名空間中執行 —— 也就是節點本身的連線能力，在資料平面介入之前。
{"command":["curl-host","-v","cloud.f5.com"]} % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying <public-ip>:80...* Connected to cloud.f5.com (<public-ip>) port 80 (#0)> GET / HTTP/1.1> Host: cloud.f5.com> User-Agent: curl/7.76.1> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 301 Moved Permanently< location: https://cloud.f5.com/< server: volt-adc< date: Mon, 03 Aug 2026 16:30:24 GMT< connection: close< content-length: 0< 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Closing connection 0curl-vega
Section titled “curl-vega”在 Vega（控制平面）情境中執行，而非主機的情境。可觀察到的差異，也是此處唯一確立的差異，是它所繼承的環境：curl-vega 會回報一份涵蓋私有網段、int.ves.io、int.volterra.us 以及站點自身 .tenant.local 網域的 NO_PROXY 清單，而 curl-host 則不會回報任何內容。這對 DNS 路徑意味著什麼，並未經過測量。
{"command":["curl-vega","-v","cloud.f5.com"]}* Uses proxy env variable NO_PROXY == '10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,100.127.0.0/18,100.127.192.0/18,169.254.0.0/16,int.ves.io,int.volterra.us,mcn-ce-ha-eastus01.<tenant>.tenant.local' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying <public-ip>:80...* Connected to cloud.f5.com (<public-ip>) port 80 (#0)> GET / HTTP/1.1> Host: cloud.f5.com> User-Agent: curl/7.76.1> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 301 Moved Permanently< location: https://cloud.f5.com/< server: volt-adc< date: Mon, 03 Aug 2026 16:30:26 GMT< connection: close< content-length: 0< 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Closing connection 0兩者都接受以獨立陣列元素形式傳入的一般 curl 參數。-v 值得保留，因為連線與 TLS 交握的輸出行通常就是失敗顯現之處。