404 response code: not able to connect to the asyncio server deployed in testing environment #1339
Unanswered
nsrawat009
asked this question in
Q&A
Replies: 1 comment 9 replies
-
Socket.IO is a bit strange in how the URL is specified. The connection URL should be your hostname followed by your namespace. So try using The path to the Socket.IO endpoint is given in the If this does not work, you should probably try to make your HTTP endpoints work first, then adapt your url and path accordingly. |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have deployed asyncio server in one of the testing environment of my firm successfully but iam not able to make connection to the server with Postman or python client although i was able to connect and get response successfully in my local testing.I dont know it is the issue with routing or incorrect url.
Iam unsure about the socketio_path arguement in ASGI app,whether i have to provide it or not since bydefault it takes socket.io path whether it should I define it inside sio_app or not??
Note:here app is another fast api app dedicated for rest endpoints
is my url correct??: (ws://nebula.nslhub.com/dsd-orch/paragraph_grammar/gsi_suggestions
Note: nebula.nslhub.com is the dns name of the environment
dsd-orch is the security layer
/paragraph_grammar/gsi_suggestions is the namespace of the event
Also i have not implemented ssl configuration yet.
Note in my microservice the request comes via istio -> kubernetes pod -> microservice -> end point
Currently iam getting 404 response code I will try removing static files which i have currently provided.What else should i check,Kindly support iam stuck
Beta Was this translation helpful? Give feedback.
All reactions