Http server connect issue about wasmedge-quickjs

[chenyukang]

FYI: second-state/dapr-wasm#17

Dapr will try to check API when starting up:

[juntao]

Could the Dapr check sends a "proper" http request with a header? The telnet request is technically not http.

[chenyukang]

Could the Dapr check sends a "proper" http request with a header? The telnet request is technically not http.

I know the reason now.
We must run the command nohup，otherwise we can not connect to server successfully.

cat@MININT-ODP168:~/code/wasmedge-quickjs/example_js$ nohup wasmedge --dir .:. ../target/wasm32-wasi/release/wasmedge_quickjs.wasm http_server_demo.js &
[1] 28385

[chenyukang]

I don't know the root cause, why do we have this limitation？

wasmedge --dir .:. ../target/wasm32-wasi/release/wasmedge_quickjs.wasm http_server_demo.js 

can not start the server properly.

[juntao]

Just to make sure -- if you do not use nohup, you will need to start the server in one terminal and run the HTTP client in another terminal window.

[chenyukang]

Just to make sure -- if you do not use nohup, you will need to start the server in one terminal and run the HTTP client in another terminal window.

I used multiple terminals to test, I guess there is a potential issue we haven't understood :)

[juntao]

@chenyukang Do both curl and telnet fail on your machine if you do not have nohup?

[chenyukang]

@chenyukang Do both curl and telnet fail on your machine if you do not have nohup?

Yes