It's not work when the server redirect 301.

[w4-hanggi]

It's ok when it return 200. but when the server return 301, cors not working.

[Louis-Amas]

this same problem using
In r.Group
Did you find a fix ?

[w4-hanggi]

@Louis-Amas I almost forget this issue, I just changed my client request to sth like .../v1/foo/
Add '/' symbol at the end of the url to prevent redirection.

[JohnyTheLittle]

Id didnt work out. I did this according to your recommendation, but client side still throws CORS error.

[llxcyzgh]

It is not caused by gin-contrib/cors, it's caused by gin.
For "TrailingSlash" redirections, the process will get out before entering any middlewares.

[RiansyahTohamba]

@Louis-Amas I almost forget this issue, I just changed my client request to sth like .../v1/foo/ Add '/' symbol at the end of the url to prevent redirection.

just in case you write '/' in the end of your url at golang server ( like /v1/foo/).

If you don't write it (like /v1/foo ), don't add '/' on your request url.

[BigBoulard]

You may want to check this answer gin-gonic/gin#1216 ...

   router := gin.New()

   friend := router.Group("/friend")
    {
      friend.GET("/", controller.GetFirends)
   }

Your router sets the handler to /friend/ path. You should use router.GET("", controller.GetFirends) if you want to use /friend :(without trailing slash).

[maczg]

You may want to check this answer gin-gonic/gin#1216

I think the issue persist even setting specific route to .GET("", controller....) and calling /at the end of the path

My workaround: duplicate routes

   router := gin.New()

   friend := router.Group("/friend")
    {
      friend.GET("/", controller.GetFirends)
     friend.GET("", controller.GetFirends)
   }

So even if you call /friendor /friend/ no 301 redirect is returned