support / in --http-upgrade-path-prefix

[GitHub4LP]

Describe the feature

ws://host:port/subpath1/subpath2/events
1.

ws://host:port -P subpath1/subpath2

2. just use whole

ws://host:port/subpath1/subpath2/

ws://host:port/subpath1/subpath2

or

http://host:port/subpath1/subpath2/

http://host:port/subpath1/subpath2

[erebe]

Hello,

Sorry for the delay, I missed the notification.
It is not supported because the path prefix is url encoded and the server take only the first part.
If I allow the path prefix to contains / the server will not know which part to take.

This can be changed I guess, but it would be a breaking change. In which use case do you need the path to contains a / ?

[GitHub4LP]

Thanks for your response. Here are some points I'd like to explain:

WebSocket inherently supports multi-level paths, so we shouldn't need to use a separate --http-upgrade-path-prefix parameter for this purpose.

Multi-level path structures (tree-like) can carry more information and enable more functionality in applications.

In deployment scenarios using reverse proxies with subpaths, the --http-upgrade-path-prefix would naturally differ between client and server sides.

Regarding compatibility: clients and servers are typically version-paired and used in matched sets, so breaking changes would affect both sides simultaneously anyway.

[laikitleung]

Using /dir as the path aligns better with CDN configurations, such as Cloudflare's default path setting, which is /dir.