tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1281752836
read my demo of wss:
https://github.com/apache/apisix/issues/5103#issuecomment-926456343
--
This is an automated message from the Apache Git Service.
To respond to the message,
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1283569807
> based on your example, websocket is okay, but socket.io is not okay.
can you provider a demo of a server that builds by socket.io, you can put
the demo in your repository
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1283572732
And I need to make sure that the client can successfully request the
server(build by socket.io) via wss without going through the APISIX proxy?
--
This is an automated message
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1284008794
I know why you get 502.
because in my demo, client --> APISIX was `wss` protocol, and APISIX to
upstream was`wss` protocol too.
in your scenes, you need client -->
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1284991776
> For this websocket example , i try to config useing ["scheme": "http"] ,
either ws or wss , It works fine
if your upstream is `listen 1983;` and use `["scheme": "http"]`
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1284995487
> but for socket.io server .it can't work .
I don't have any more ideas either, I don't know what special differences
there are in socket.io. If you want me to continue inv
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1286540518
I investigated a bit and found some differences by grabbing the packets
without looking deeper.
I saw this: https://socket.io/docs/v4/#what-socketio-is-not
--
This is an
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1286674146
> thank you, they are not the same. so apisix doesn't support socket.io yet ?
I don't know how to support it now
--
This is an automated message from the Apache Git Servi
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1286717394
> @jackyzhao001 Is it possible for you to capture some WebSocket frame
packets? So that we can analyze this problem further.
I caught the package, we can look at it togethe
tzssangglass commented on issue #8093:
URL: https://github.com/apache/apisix/issues/8093#issuecomment-1286727731
[sio-cap.zip](https://github.com/apache/apisix/files/9837861/sio-cap.zip)
sio-raw.cap is socket.io client connect socker.io server directly
sio-apisix is socket.io client
10 matches
Mail list logo
