Custom headers is allowed in V2ray WebSocket transport. However for Shadowsocks outbounds, currently it's not possible to configure them through plugin_opts.
Setting User-Agent (or other headers) might be useful for server to distinguish clients (e.g. identifying sing-box client against web browsers / scrapers) so the sever can then choose to provide service or not.
It's not hard to read an additional argument from plugin_opts and apply it to option.V2RayTransportOptions. I made a simple patch as below and it's working.
Support. Looking forward to the update merge.
Looking forward to shadowsocks support
I am currently using simple-obfs to reverse the generation, and I am tired
Custom headers is allowed in V2ray WebSocket transport. However for Shadowsocks outbounds, currently it's not possible to configure them through
plugin_opts
.Setting
User-Agent
(or other headers) might be useful for server to distinguish clients (e.g. identifying sing-box client against web browsers / scrapers) so the sever can then choose to provide service or not.It's not hard to read an additional argument from
plugin_opts
and apply it tooption.V2RayTransportOptions
. I made a simple patch as below and it's working.