CORS VS Fiber

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.

To make my life easier, I added Fiber, a popular lightweight framework. Regardless of which package you use, the process and most of the code will remain unchanged.

Since you're from Nodejs just like me, I use fiber https://gofiber.io/ it's easier to understand from a Nodejs background (express, etc) and there's nothing wrong using it if you know it, your casual application wont need all the performance in the world Go provides

I think u should try Fiber it's the fastest according to the benchmarks and imo it's the best I love it!!!

Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.

Fiber

Fibber is web framework written in Go. It is very easy to learn. https://gofiber.io

don’t have an API at all - it’s a security vulnerability and unless you already know how to secure an API suite it’s very likely to increase risk for a dependent project. if you’re set on an API, use a well known routing package (e.g I love gofiber), and add an optional .withMiddleware() to your start func to allow clients to extend and secure the API themselves

I have loved using fiber. Very nice API with lots of configurability and it scales very well compared to echo, gin, etc.