-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cors-anywhere has been closed down #7
Comments
Hi @ErikKnowles thank you for your issue. I have checked the CORS anywhere just now and it's still online. Can you confirm again? |
The url responds, but it does not accept traffic on the api endpoint. See: https://github.com/Rob--W/cors-anywhere/issues/301
I'm using a fork of this repo deployed to Heroku: https://github.com/iamkentleom/tinyurl-rest-wrapper
Works fine.
- Erik
On 2/10/2021 21:28:10, mpj <[email protected]> wrote:
Hi @ErikKnowles [https://github.com/ErikKnowles] thank you for your issue. I have checked the CORS anywhere just now and it's still online. Can you confirm again?
https://cors-anywhere.herokuapp.com/ [https://cors-anywhere.herokuapp.com/]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [#7 (comment)], or unsubscribe [https://github.com/notifications/unsubscribe-auth/ABJAQEAE4QKQU5DTJOSAJYTS6NMFVANCNFSM4XNZC53Q].
|
noted, I'll prioritize to update the client then. |
Fix is on the way. @yuliefas will take a look. |
This is related to this as well kulkultech/ngecilin#37 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The cors-anywhere Heroku service was recently shut down, so you'll need another CORS workaround method.
The text was updated successfully, but these errors were encountered: