3 ms·
Given that http://susam.net:8000 http://susam.net:8000 has stopped responding, I suspect that there will be a lot more beeps today.
by pwagland 1y ago
Given that http://susam.net:8000 http://susam.net:8000 has stopped responding, I suspect that there will be a lot more beeps today.
- pekim 1y agoIt's not an http server. Try with something like nc or telnet, and you should get an 'ok' response before it disconnects. telnet -4 susam.net 8000
- baxtr 1y agoFrom the article: > The other party can use whatever client they have to connect to port 8000 of my system, e.g., a web browser, nc HOST 8000, curl HOST:8000, or even, ssh HOST -p 8000, irssi -c HOST -p 8000, etc.
- collinvandyck76 1y agoTo get an OK I had to force curl to use http 0.9 > curl -v --http0.9 susam.net:8000
- pekim 1y agoOops, that'll teach me to read articles properly before commenting, rather than just skimming.
- lukan 1y agoNow I feel a bit like writing some tool to automatically follow your posts (easy with existing HN replies) do a semantic analysis on them to determine when you will make that misstake again and give some alert (the hard/expensive part).
- thesuitonym 1y agoMaybe the alert could be four beeps on your terminal
- lukan 1y agoAnd then I write a blog post about it. But maybe I find something more novel. (And I have, but maybe I can actually use it for the task above)
- deleted 1y ago[deleted]
- nom 1y agoI got an ok!
- dgacmu 1y agoGot 2 ok's out of about 14 attempts. ;)