-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
feature request: enable CORS #1500
Comments
signal-cli doesn't have any kind of authentication, so just accessing it from a web browser is not advisable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use signal-cli to send messages to Signal in my NUXT3 project and encountered a problem where I cannot use signal-cli directly as a JSON-RPC --http endpoint. If I use 'mode: 'no-cors'', signal-cli gives an error Http 415 Unsupported Media type because with 'mode: 'no-cors'', the header is always set as 'Content-Type' as 'text/plain' and ignores the explicitly specified header 'Content-Type': 'application/json'; otherwise, we have CORS problems if we don't use 'mode: 'no-cors''.
It would be wonderful to include CORS support in your creation.
Thank you very much!
https://developer.mozilla.org/en-US/docs/Glossary/CORS
The text was updated successfully, but these errors were encountered: