Bug with underlying gin-wraphh module causes 404 to not work properly

[scr-oath]

• See WrapHH should put the Writer back after calling c.Next() turtlemonvh/gin-wraphh#7

Basically, if you add compression middleware, any 404 not found calls result in an error because the 404 is handled after the entire gin.HandlerChain has attempted to process.

(oath_tools) [scr@MacBook-Pro-3]$ curl --compressed localhost:4080/
curl: (52) Empty reply from server

In order to fix this, the issue above would need to be addressed or you would need to roll your own WrapHH as in the PR turtlemonvh/gin-wraphh#8