BoazDr opened a new issue #5103:
URL: https://github.com/apache/apisix/issues/5103


   ### Issue description
   
   I am trying to add an API Gateway to a client-server system, which 
communicates through WebSockets.
   
   The Server is an audio recognition engine that sits in a remote machine, and 
clients are connecting to it through WebSockets ('wss://...'), sending audio 
files and receiving their text translate representation. My main goal is to add 
a free open-source API Gateway in the middle in order to 
authenticate\authorize\rate limit\etc...
   After searching the web, I focused on Apache APISIX gateway. As a test, I 
managed to connect the APISIX to a client-server which communicates by 
http/https and it worked fine.
   
   I'm wondering if anyone knows from experience if it's possible to use 
WebSockets with Apache APISIX and if yes, how exactly it should be done (a 
little example would go a long way) - because the docs are missing any 
informative info\examples, or if there are better solutions known to my problem.
   
   ### Environment
   
   - apisix version (cmd: `apisix version`): Installed the whole project 
through docker-compose, all versions are the most recent from official apache 
APISIX docs.
   - OS (cmd: `uname -a`): Linux Centos 7
   - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):
   - etcd version, if have (cmd: run `curl 
http://127.0.0.1:9090/v1/server_info` to get the info from server-info API):
   - apisix-dashboard version, if have:
   - the plugin runner version, if the issue is about a plugin runner (cmd: 
depended on the kind of runner):
   - luarocks version, if the issue is about installation (cmd: `luarocks 
--version`):
   
   The only Web socket reference there is in the dashboard:
   
   ![websocket 
apisix](https://user-images.githubusercontent.com/49284948/133920881-a42ba79f-9efe-4b0e-a341-35761ef01b51.PNG)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to