[DISCUSS] I think we should move enable_web_socket to routes rather in plugin

[????Lien]

   
     I think the websocket usually means a upstream server that 
serve as websocket server.
     which I think we could move the websocket function enable 
button to upstream configration page.
   
     the idea that move the websocket controller to upstream is 
from Cloud Service.    


    I  used Alibaba cloud DCDN service before, after setup the 
DCDN(dynamic CDN) domain and upstream, it cloud indicate that whether support 
websocket function??



Mail from Lien


 




------------------ ???????? ------------------
??????:&nbsp;"????Lien"<lilien3...@qq.com&gt;;
????????:&nbsp;2019??11??3??(??????) ????5:40
??????:&nbsp;"dev"<dev@apisix.apache.org&gt;;

????:&nbsp;[DISCUSS] I think we should move enable_web_socket to routes rather 
in plugin



&nbsp; &nbsp; Hi guys, 
&nbsp; &nbsp; for now the web socket&nbsp; enable button is hidden in 
proxy-rewrite plugin, which I think is very inconvenient for users to put a 
web-socket server behind APISIX.
&nbsp; &nbsp;proxy-write is more like NGINX parameter modifier, rather than 
service or function controller to enable or disable some features.
&nbsp;
&nbsp; &nbsp;Scenario:
&nbsp; &nbsp;When I have a web socket server explode URI like this 
/web_socket/123456,(123456 is a URI var)??
&nbsp; &nbsp;then I create a router&nbsp; /web_socket/*.
&nbsp; &nbsp;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 .

&nbsp;
&nbsp; 

Mail from Lien@HelloTalk


&nbsp;
&nbsp;