NewV2 method cause 404 error，but the New method is ok

[wangliguokaka]

code： func main() {

http.HandleFunc("/ok", func(w http.ResponseWriter, r *http.Request) {
    w.Header().Add("Content-Type", "application/json")

    w.WriteHeader(200)
    io.WriteString(w, "ok")

})

http.HandleFunc("/test", func(w http.ResponseWriter, r *http.Request) {
    w.Header().Add("Content-Type", "application/json")

    w.WriteHeader(200)
    io.WriteString(w, "test")
})

lambda.Start(httpadapter.NewV2(http.DefaultServeMux).ProxyWithContext)

}

error ：

[rajrohanyadav]

Hi, I'm also facing exactly the same issue with my API. I debugged and found, that when using NewV2, it puts a test/ before the actual requested path, which causes the 404. e.g. Expected req path: req.RequestContext.HTTP.Path = /api/v1/cats Actual req path: req.RequestContext.HTTP.Path = /test/api/v1/cats

EDIT: With SAM local, the req path is formed correctly and all the API endpoints are reached fine. But after deployment to AWS API Gateway it doesn't seem to work. (I'm using AWS::Serverless::HttpApi)

[esoteloferry]

I have same issue with HTTP (v2) gateway but adding test did not work @rajrohanyadav

@wangliguokaka did you find a solution you can share?