Simple, secure & standards compliant web server for the most demanding of applications
-
Updated
Jul 20, 2021 - C++
And go vet
doesn't like it
Error: ./protocol_test.go:29:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:37:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:40:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:88:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:99:4: call to (*T).Fa
Add a description, image, and links to the proxy-protocol topic page so that developers can more easily learn about it.
To associate your repository with the proxy-protocol topic, visit your repo's landing page and select "manage topics."
Currently we have a mix of:
Out of memory error.
Out of memory error
out of memory error
out of memory
out of memory.
out of memory [some context]
All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller😄