request help: websocket tab is lost in 2.0rc2？

[souzens]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [yes ] Bug

update to 2.0rc2 . websocket tab is lost in step one。
Has this feature been removed？

[juzhiyuan]

Ya, from 1.5 to 2.0, we have removed some features which originally belong to plugins, you could find them in plugin page.

[juzhiyuan]

But note, currently, in plugin page, some of them have UI issues, we are going to resolve all of them in 2.1 soon.

[juzhiyuan]

according to current tasks, this enhancement feature will resolve in 2.3.

[iyuhptop]

which plugin should select for websocket

[moonming]

no plugin need weboscket，which is binding with router

[juzhiyuan]

I see, i will check this ASAP.

[juzhiyuan]

in Route.

[juzhiyuan]

[juzhiyuan]

https://github.com/apache/apisix/pull/2836/files#diff-ebd29c155b76d68bb1cd728cd626f281f81c62ddb451b345baf2ed8f81480127R378

Hi @membphis, I see there has a tip saying the enable_websocket field will be removed soon, do we have any plan?

[moonming]

Will be removed in 2.3 琚致远 <[email protected]>于2020年12月13日 周日下午5:07写道：

https://github.com/apache/apisix/pull/2836/files#diff-ebd29c155b76d68bb1cd728cd626f281f81c62ddb451b345baf2ed8f81480127R378 [image: image] <https://user-images.githubusercontent.com/2106987/102007595-7e9ad680-3d65-11eb-8e86-3edb3ccdc2eb.png> Hi @membphis <https://github.com/membphis>, I see there has a tip saying the enable_websocket field will be removed soon, do we have any plan? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#831 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJZBK5HYS4RGXHLOZEAEXTSUR73PANCNFSM4T3BLYBA> .

-- Thanks, Ming Wen Twitter: _WenMing

[juzhiyuan]

I couldn't find milestone 2.3, you mean 3.0 or 2.3 has not been created?

https://github.com/apache/apisix/milestones

[juzhiyuan]

The frontend will still use that field for now.

[moonming]

no, FE should not use it in upstream 琚致远 <[email protected]>于2020年12月13日 周日下午6:30写道：

The frontend will still use that field for now. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#831 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJZBK7BI4YGKBU36LZLCL3SUSJTVANCNFSM4T3BLYBA> .

-- Thanks, Ming Wen Twitter: _WenMing

[moonming]

Websocket is binding with route now Ming Wen <[email protected]>于2020年12月13日 周日下午6:47写道：

no, FE should not use it in upstream 琚致远 ***@***.***>于2020年12月13日 周日下午6:30写道： > The frontend will still use that field for now. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#831 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGJZBK7BI4YGKBU36LZLCL3SUSJTVANCNFSM4T3BLYBA> > . > -- Thanks, Ming Wen Twitter: _WenMing

-- Thanks, Ming Wen Twitter: _WenMing

[moonming]

Please check the Chang log of apisix for detail Ming Wen <[email protected]>于2020年12月13日 周日下午6:48写道：

Websocket is binding with route now Ming Wen ***@***.***>于2020年12月13日 周日下午6:47写道： > no, FE should not use it in upstream > > 琚致远 ***@***.***>于2020年12月13日 周日下午6:30写道： > >> The frontend will still use that field for now. >> >> — >> You are receiving this because you commented. >> Reply to this email directly, view it on GitHub >> <#831 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AGJZBK7BI4YGKBU36LZLCL3SUSJTVANCNFSM4T3BLYBA> >> . >> > -- > Thanks, > Ming Wen > Twitter: _WenMing > -- Thanks, Ming Wen Twitter: _WenMing

-- Thanks, Ming Wen Twitter: _WenMing

[juzhiyuan]

Websocket is binding with route now

Ming Wen [email protected]于2020年12月13日 周日下午6:47写道：

no, FE should not use it in upstream

琚致远 [email protected]于2020年12月13日 周日下午6:30写道：

The frontend will still use that field for now.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#831 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGJZBK7BI4YGKBU36LZLCL3SUSJTVANCNFSM4T3BLYBA
.

--
Thanks,
Ming Wen
Twitter: _WenMing

--
Thanks,
Ming Wen
Twitter: _WenMing

Ok, now i know what happened, i heard from @membphis that this field is bound to Route and called enable_websocket, but when i saw that PR, i didn't see that change is related to upstream_def until you point out.

Conclusion: The frontend will use that field with Route instead of Upstream.

[membphis]

Conclusion: The frontend will use that field with Route instead of Upstream.

yes, that is right