- refactored MessageChannel and HTTPChannel do perform the processing
- added setOptions support
- moved connection related header handling to HttpChannel
- added basic event infrastructure to provide hooks for certain events where extending classes may act upon
- added Bad Request response on parsing errors (events)
- made staticContentHandler more restrictive on which requests to serve
- and some tests
added wait cycle
modified port checking
fixed port pre-condition verification
- added support for custom configurations
- improved unit test coverage
- added support to shutdown server
- added tests
- fixed keep alive behavior
fixed built-in standard port to match build server environment
Merge pull request #6 from gmuecke/AWTT-22-Response-with-BAD-Request-on-Protocol-Exception

Awtt 22 response with bad request on protocol exception