Cors problem in deployment (react + go)
Helo people, I'm aware there's been bunch of similar issue presented and resolved, yet I did all I could and still no luck.
project ID:
443e27d8-9cdf-478d-a4ec-c846823facf8
I'm getting
I got below config in go:
and making request like below from the react:
(to https url)
Solution:Jump to solution
Here is the code I used, I was not able to reproduce the issue, even with cloudflare in front -
```gopackage main
import (
"cmp"...
18 Replies
Project ID:
443e27d8-9cdf-478d-a4ec-c846823facf8
what is
NEXT_PUBLIC_API_URL
set to?https://api.diplomacy.network
without trailing /
have you confirmed that headers are being set locally?
no headers set by the react explicitly, but seeing some req headers set on the browser ( @ local)
react is a framework, its not going to be setting headers, can you elaborate on what you mean by that?
all the headers we got are set automatically by the browser. none I've additionally set via axios library
im sorry but that isnt answering the questions ive asked
have you confirmed that CORS headers are being set locally?
I haven't manualy set any so far. But now I've set below and didn't change anything.
This also does not answer the question, im not sure where the confusion is coming from?
ill try to clarify further, have you confirmed that your go backend setting the cors headers when testing locally?
yes locally my go backend sets access-control-allow origin as localhost:3000 (my react app) successfully.
and that's not the case when I switch to prod endpoint
would that be a revelant response @Brody ?
what go web framework and middleware for cors are you using? I'll try to get a reproducible example going
hey I'm using gorilla for cors config
here is the code:
https://github.com/demo-verse/proof-of-peacemaking-generator/blob/main/main.go
GitHub
proof-of-peacemaking-generator/main.go at main · demo-verse/proof-o...
A simple web tool to generate Proof of Peacemaking certificates (work in progress) - demo-verse/proof-of-peacemaking-generator
I thought gorilla had an easy way to chain middlewares
Solution
Here is the code I used, I was not able to reproduce the issue, even with cloudflare in front -
perhaps you have something missconfigured with cloudflare? either way, this would not be an issue with Railway