Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vercel is not sending CRON_SECRET in Authorization header of cron request #11303

Open
GonzaloAszyn opened this issue Mar 20, 2024 · 0 comments
Open

Comments

@GonzaloAszyn
Copy link

From one moment to another, with a deployment that did not touch anything near to cron requests or vercel.json, now cron requests are not receiving the CRON_SECRET variable and thus it resolves in 403. I could get rid of the security but I don´t want my crons to be publicly available.

image

this is how my code for checking the authorization header looks. It has worked perfectly for months, and it works locally. But suddenly now it does not work on production as authorization header is undefined.

Really need to know what is going on. I'm working with Node.Js express

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant