Mishandling 404?

[rymurr]

I have a simple program

package main

import (

	"github.com/gin-contrib/gzip"
	"github.com/gin-gonic/gin"
)

func main() {
	r := gin.New()
	r.Use( gzip.Gzip(gzip.DefaultCompression))

	r.GET("/x", func(c *gin.Context) {
		c.JSON(200, gin.H{"hello": "world"})
	})
	r.Run()
}

when i do curl localhost:8080 -H 'accept-encoding: gzip' -v I get a 200 response and when I do curl localhost:8080 -v I get a 404 response.

I am not sure what I am doing wrong but it seems like the gzip buffer is being closed before gin writes its 404 which somehow messes up the eventual response object.

hitting the localhost:8080/x endpoint works fine

[rymurr]

It looks like this was introduced between v1.0.1 and v1.1.0

[cloudberrystory]

Same stuff

[Kerguillec]

Hello, same here
Also with debug mode I got the following error with a 200 answer instead of 404 while hitting bad route (since v1.10) :
[GIN-debug] cannot write message to writer during serve error: flate: closed writer
I don't know if it's related

[aveyuan]

module gingz

go 1.23.6

require (
	github.com/gin-contrib/gzip v1.2.2
	github.com/gin-gonic/gin v1.10.0
)

It's work

[joshelser]

It's work

The bug is that http://localhost:8080/ should return a 404 but it returns a 200. Requests to http://localhost:8080/x work as expected.

[aveyuan]

It's work

The bug is that http://localhost:8080/ should return a 404 but it returns a 200. Requests to http://localhost:8080/x work as expected.

Look at it's nothing?

[aveyuan]

？body response is large ,the gzip will error？