Is your feature request related to a problem? Please describe.
When I setup the webrtc-streamer (s), the client doesn't have static ip address. (behind a DHCP).
So I use a cloud server with FRPS, and FRPC on webrtc-streamer client, then I can call the api through FRPS(cloud server).
Since I have multiple webrtc-streamer clients in different places. So if I can use different /location (prefix for /api), It will be convenient for me, I don't need to pre-process the request(/locationa /locationb /locationc) with another tool, and I can reverse proxy only one port for FRP.
Describe the solution you'd like
Support -H host:port/location. Or another opt like -H host:port -L base_path => host:port/base_path/api/...
Describe alternatives you've considered
Currently doesn't have an alternative.
Is your feature request related to a problem? Please describe. When I setup the webrtc-streamer (s), the client doesn't have static ip address. (behind a DHCP). So I use a cloud server with FRPS, and FRPC on webrtc-streamer client, then I can call the api through FRPS(cloud server).
Since I have multiple webrtc-streamer clients in different places. So if I can use different /location (prefix for /api), It will be convenient for me, I don't need to pre-process the request(/locationa /locationb /locationc) with another tool, and I can reverse proxy only one port for FRP.
Describe the solution you'd like Support -H host:port/location. Or another opt like -H host:port -L base_path => host:port/base_path/api/...
Describe alternatives you've considered Currently doesn't have an alternative.