Addresses which fail to resolve are handled more gracefully in the two most common cases: the hostname doesn't resolve or the port is unknown (like "http" on a system that doesn't support that port name). If the hostname doesn't resolve, the host is served on the listener at host 0.0.0.0. If the port is unknown, we attempt to rewrite it as a number manually and try again.

Test for webSocketParse function in config/setup

Modularizing config/setup/Websocket.go and test file for the same

errors: change missing errors file from error to a warning during parsing

browse: Ability to sort

setup: export functions and variables for external packages.

Tests for config/setup/internal.go

Tests for config/setup/log.go

fastcgi: fix #127

ext: test for function extParse

log: ensure the correct status is always logged

in the case of error (>=400) then no response may have been sent

Preliminary test case for setup/config/ext.go

Update with missing assertion for the Next middleware being properly set , this makes sure that Ext middleware carries the requests to the further middlewares .

Added assertions to check for the extensions in the order specified

middleware: let middleware.responseRecorder be a http.Hijacker

Signed-off-by: Tw <tw19881113@gmail.com>