You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I connect to server using wscat it just halts the socket and wscat reports "404". But is I try to send a simple http request (which is a part of ws handshake process) socket halts with no response:
root@32c3b8cb3c23:/# curl -vv http://localhost:8001/subgraphs/name/kittycatdao/zksync* Expire in 0 ms for 6 (transfer 0x55896a3be0f0)
* Expire in 1 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 0 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 2 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 0 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 1 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 4 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 1 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 2 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 8 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 3 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 3 ms for 1 (transfer 0x55896a3be0f0)
* Expire in 4 ms for 1 (transfer 0x55896a3be0f0)
* Trying 127.0.0.1...
* TCP_NODELAY set* Expire in 149993 ms for 3 (transfer 0x55896a3be0f0)
* Expire in 200 ms for 4 (transfer 0x55896a3be0f0)
* Connected to localhost (127.0.0.1) port 8001 (#0)> GET /subgraphs/name/dao/zksync HTTP/1.1
> Host: localhost:8001
> User-Agent: curl/7.64.0
> Accept: */*>* Empty reply from server
* Connection #0 to host localhost left intact
curl: (52) Empty reply from server
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Deploy graph node in docker container
Deploy subgraph
Connect to node docker container using docker exec
Install nodejs and curl
run npx wscat -c ws://localhost:8001/subgraph/<deployed-subgraph> or curl http://localhost:8001/subrgaph/<deployed-subgraph>
What is the expected behavior?
Server send HTTP 101 Switch Protocols response at least.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
It's a Bug
What is the current behavior?
When I connect to server using wscat it just halts the socket and wscat reports "404". But is I try to send a simple http request (which is a part of ws handshake process) socket halts with no response:
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
docker exec
npx wscat -c ws://localhost:8001/subgraph/<deployed-subgraph>
orcurl http://localhost:8001/subrgaph/<deployed-subgraph>
What is the expected behavior?
Server send
HTTP 101 Switch Protocols
response at least.The text was updated successfully, but these errors were encountered: