Dear, 李凌Lien Because everyone's use scenarios are different. If it is configured in the upstream module, the upstream can only be used as websocket service. The current configuration mode will be more flexible than that in upstream. But you mentioned that rewriting URIs to support fuzzy matching is a good idea.
李凌Lien <[email protected]> 于2019年11月3日周日 下午5:43写道： > Hi guys, > for now the web socket enable button is hidden in proxy-rewrite > plugin, which I think is very inconvenient for users to put a web-socket > server behind APISIX. > proxy-write is more like NGINX parameter modifier, rather than service > or function controller to enable or disable some features. > > Scenario: > When I have a web socket server explode URI like this > /web_socket/123456,(123456 is a URI var)。 > then I create a router /web_socket/*. > here comes the problem if I use proxy-write, no doubt I want keep the > URI same to backend server while enable the web-socket . > > > > > Mail from Lien@HelloTalk
