b157d4ebb2
Previously we did not check HTTP semantics and it is left out for application. Although checking is relatively easy, but they are scattered and error prone. We have implemented these checks in our applications and also feel they are tedious. To make application development a bit easier, this commit adds basic HTTP semantics validation to library code. We do following checks: server: * HEADERS is either request header or trailer header. Other type of header is disallowed. client: * HEADERS is either zero or more non-final response header or final response header or trailer header. Other type of header is disallowed. For both: * Check mandatory pseudo header fields. * Make sure that content-length matches the amount of DATA we received. If validation fails, RST_STREAM of type PROTOCOL_ERROR is issued. |
||
|---|---|---|
| .. | ||
| Makefile.am | ||
| alt-server.crt | ||
| alt-server.key | ||
| config.go.in | ||
| nghttpx_http1_test.go | ||
| nghttpx_http2_test.go | ||
| nghttpx_spdy_test.go | ||
| server.crt | ||
| server.key | ||
| server_tester.go | ||
| setenv.in | ||