Short answer

HTTP and SOCKS are basic outbound proxy types, often used for chaining, LAN gateways or connecting Clash to an existing proxy. In real use, trust the provider subscription first and then verify whether the selected client core supports this exact type.

What It Means

In Clash/Mihomo configuration, http / socks identifies the outbound type used by the node, policy or group. The same display name in a GUI can hide different transport fields, so the YAML or subscription output is more reliable than the node nickname.

Common Fields

type: http / socks
server / port
username / password
tls
sni
udp

When to Use It

Traffic needs to be forwarded to an existing HTTP/SOCKS proxy.
A local or LAN proxy port already exists.
Support Checks benefits from the simplest upstream proxy shape.

Support Checks Checks

HTTP/SOCKS by themselves are not encrypted tunnels.
Username/password and TLS settings depend on the upstream proxy.
SOCKS UDP support depends on both server and client.

Minimal Shape

proxies:
- name: "socks-upstream"
  type: socks5
  server: 127.0.0.1
  port: 1080
  username: user
  password: pass
  udp: true

Compatibility Notes

Client support changes with the bundled core. A maintained Mihomo-based client usually supports more modern node types than historical Clash clients, but mobile clients and iOS alternatives still vary by app and release.

If a subscription contains this type but the client filters it out, switch to a compatible client, ask the provider for a compatible subscription format, or use a converter only when you understand what fields are being changed.

Official Reference

HTTP / SOCKS in Mihomo docs SOCKS

HTTP / SOCKS Protocol