WunderkindNYC/lbmlp-caddy: caddyhttp/websocket/websocket.go; 5 LoC

Found a possible issue in [WunderkindNYC/lbmlp-caddy](https://www.github.com/WunderkindNYC/lbmlp-caddy) at [caddyhttp/websocket/websocket.go](https://github.com/WunderkindNYC/lbmlp-caddy/blob/ad4e5371f087952447f9eafc3457d78526596ba9/caddyhttp/websocket/websocket.go#L83-L87)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.

> function call which takes a reference to sockconfig at line 85 may start a goroutine

[Click here to see the code in its original context.](https://github.com/WunderkindNYC/lbmlp-caddy/blob/ad4e5371f087952447f9eafc3457d78526596ba9/caddyhttp/websocket/websocket.go#L83-L87)

Click here to show the 5 line(s) of Go which triggered the analyzer.

```go
for _, sockconfig := range ws.Sockets {
if httpserver.Path(r.URL.Path).Matches(sockconfig.Path) {
return serveWS(w, r, &sockconfig)
}
}

```

Click here to show extra information the analyzer produced.

```
The following graphviz dot graph describes paths through the callgraph that could lead to a function calling a goroutine:
digraph G {
"(serveWS, 3)" -> {"(pumpStdout, 3)";}
"(pumpStdout, 3)" -> {}
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: ad4e5371f087952447f9eafc3457d78526596ba9