Client-side Acceptable Format Initiative

Stage: Proposal

This initiative hopes to improve the current situation of Proxy Client based on User-Agent detection format.

The initiative recommended use Accept http request header

Example

Request:

GET /to/path HTTP/1.1
Accept: text/clash+yaml, text/surge

Response:

HTTP/1.1 200 OK
Content-Type: text/clash+yaml

Media Type Registry

Media Type	File Format
text/surge	Surge format
text/surge-proxies	Surge Proxy Provider format
text/surge-ruleset	Surge Rule Provider format
text/surge-domain-set	Surge Domain Set format
text/clash+yaml	Clash format
text/clash-proxies+yaml	Clash Proxy Provider format
text/clash-ruleset+yaml	Clash Rule Provider format (YAML)
text/clash-ruleset	Clash Rule Provider format (Text)
text/sip008+json	Shadowsocks SIP008 format
text/uri-proxies	URI Proxies format

References

• RFC 2046, section 4.1
• RFC 2048, section 2.1.4
• RFC 2483, section 5
• RFC 6839, section 3.1
• RFC 6648
• YAML Media Type, section 2.2
• List of Proxy URI scheme