Skip to content

philipjscott/nginx-ws

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

What is this?

A demo of NGINX killing websocket connections if pings aren't sent from the application server.

Created for nhooyr/websocket#265

Getting started

Make sure you've installed Docker, Go, and some websocket client (I use websocat).

Run the Go websocket server on port 8081:

go run main.go

Then, run NGINX on port 8080:

docker-compose up

The Go websocket server is an echo server. Try connecting directly to the Go server:

websocat ws://127.0.0.1:8081
foo
foo

Neat. This connection should last indefinitely. Now try connecting to the NGINX server:

websocat ws://127.0.0.1:8080
foo
foo

Neat. If you wait 60 seconds, and attempt to send another message, you won't get an echo. If you attempt to send another message, you'll get the following error (NGINX killed the connection):

websocat: WebSocketError: I/O failure
websocat: error running

About

NGINX + Websocket ping demos

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages