I have several netlify functions configured. One of them, just one of them, is giving me the dreaded HTTP 302 response CORS error when consumed from a browser on another domain. All my netlify function endpoints are configured in the netlify.toml file and all follow the following format: [[redirec…

Could you share the link of the page calling the API endpoint?

I’m calling it from localhost

if you are calling it from localhost, it makes sense that you would be receiving a CORS issue. if you deploy, are you able to call the function?

Not so. The Access-Control-Allow-Origin = "*" response header is there to allow access from anywhere. So my issue is this. /api/gift/:txHash fails with a CORS error HOWEVER if I hit /.netlify/functions/gift?txHash=:txHash directly it works perfectly. This fact means there MUST then be something wr…

This may have absolutely nothing to do with it, but have you tried testing it without the 301 redirect? Along the lines of: [[redirects]] from = "/api/gift/:txHash" to = "/.netlify/functions/gift?txHash=:txHash" status = 200

If I make this change then the endpoint https://cryptomint.one/api/gift/some-test-tx-hash returns a 404. Which is not at all what I would have hoped for. Hitting https://cryptomint.one/.netlify/functions/gift?txHash=some-test-tx-hash works as expected

That seems like it should work to me, but looking at this thread there may be some limitations with rewrites to functions I wasn’t aware of: [image] queryStringParameters not working with redirect on production Support Hey there, We put this question to the team who work…

Also, I can see a weird configuration. You’ve this: [[redirects]] from = "/api/gift/:txHash" to = "/api/_gift?txHash=:txHash" status = 200 [[redirects]] from = "/api/_gift" to = "/.netlify/functions/gift" force = true status = 200 You’re using double proxy, that is /api/gift/ to /a…

@hrishikesh Can you confirm why the following doesn’t work? (For my own interest) [[redirects]] from = "/api/gift/:txHash" to = "/.netlify/functions/gift?txHash=:txHash" status = 200 Does the rewrites engine not support placeholder values being passed into named query string parameters…

From my testing it does not @nathanmartin . Agree with @hrishikesh ’s final redirect and usage example @eddyoc which is the only way I have found to make this work.

Dreaded CORS issue on netlify function

Support

nathanmartin November 6, 2021, 2:43pm 8

That seems like it should work to me, but looking at this thread there may be some limitations with rewrites to functions I wasn’t aware of:

Topic		Replies	Views
Access-Control-Allow-Origin Policy Support authentication , cors	74	64018	March 5, 2024
Redirect CORS issue Support lambda-functions , redirects , cors	3	1855	October 11, 2022
Redirect to function on another Netlify site Support lambda-functions , redirects	3	913	November 8, 2020
Redirects effecting lambda functions Support lambda-functions	13	2104	August 14, 2019
Redirects to function endpoints not working using netlify cli "netlify dev" Support netlify-cli , redirects	8	2438	May 16, 2020

Dreaded CORS issue on netlify function

Related topics