Hi: You just listed the CDN scenario, but we are an API gateway.
Using enable_websocket as an upstream option may be wrong. For the grpc protocol, there is no such option. On Tue, Nov 5, 2019 at 11:14 PM 李凌Lien <[email protected]> wrote: > > 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 > > > > > > > > ------------------ 原始邮件 ------------------ > 发件人: "李凌Lien"<[email protected]>; > 发送时间: 2019年11月3日(星期天) 下午5:40 > 收件人: "dev"<[email protected]>; > > 主题: [DISCUSS] I think we should move enable_web_socket to routes > rather in plugin > > > > 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 > > > > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
