CORS VS go-webview2

And, you could find some cors knowledge on https://github.com/rs/cors

We have REST services that need to be used with the browser, We configured these HTTP Golang services to handle CORS using cors package.

Give it a try to this library https://github.com/rs/cors and put the middleware in your router.

I'm learning Go, so I made a pretty simple rest api, now I want to use it in a React frontent, I decided to use the github.com/rs/cors library, using the default configuration of this library everything works fine, but when I add "AllowedOrigins":

rs/cors - GitHub

Now, for CORS I am currently using the rs/cors package, but noticed that it has the whole gin-gonic/gin library as a dependency. I found gin-chi/cors which has no dependency at all but seems to do the same thing.

The only thing missing is a more dynamic router, and this is where we have the usefulness of being able to pick a small, focused library for it (e.g. gorilla/mux). The base package is also highly interoperable with middleware (e.g. rs/cors for managing CORS headers), so in most cases it is easier to just pick out the features you want and compose them on top of net/http (or write them yourself), rather than find a framework that does it all.

Hello, I am new to go and I have created a mux server using gorm. I am using the cors go library to enable cors. I have added a vue/nuxt frontend and all my routes are working fine. However, I have been trying to integrate react-admin and I am getting cors issues only on PUT requests. Could someone help me figure out what the issue is. Thanks.

It might be a function of the fact that the project had a hand crafted main rather than using the generated one, but when I hit this for adding CORS to a go-swagger project we used a handler generated by rs/cors as middleware - it (and a bunch of other middleware) wrapped the generated server's handler as go-swagger uses one root handler.

take a look at go-webview2, Wails uses it on their projects

jchv/go-webview2 - GitHub