Skip to content

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

Description

@scr-oath

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions