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 #736
CORS #736
Conversation
…nto feature/async_protocols
…nto feature/async_protocols
…nto feature/async_protocols
I guess I should rebase on origin? maybe just cherry-pick that commit if you want it? |
Looks good, thanks ! If I understand correctly this means that a web page on e.g. example.com will accept to do a request to an oscquery server located at bar.com:1234, right ? |
indeed since it's one line I'll just cherry-pick it on master |
I imagine there are some security implications around this, I'll add it to the (upcoming) github kanban board regarding network security in libossia so that we can review more in depth if for instance there are settings that should be provided to the user, etc... in the meantime thanks for the patch ! |
yeah, its a browser that controls the acceptance or not but, exactly... a webpage served from the |
yeah, maybe this would want to be a configurable thing eventually.. but in the short term, i'm excited to make some web based UI for my libossia based project! |
This allows for browser based requests to a libossia http server... so that we can create browser based UIs that do OSCQuery discovery.
https://developer.mozilla.org/en-US/docs/Glossary/CORS