-
Notifications
You must be signed in to change notification settings - Fork 78
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
Upload Acces-Control-Access-Origin Error #38
Comments
It sounds like you are trying to use this library from your browser? Is this correct? (maybe with browserify or something). |
Yes the API is being called from javascript which is running in the browser. Is that not supported? |
For some more information: the web app has a django backend and is using webpack to build the javascript files (react frontend) to then be loaded in the html templates. |
Correct, we don't currently support using this library in the client. I believe we have seen this error in the past though, so I'll have our developers dig in further and see why you can't make an AJAX call to /me/videos. |
So if I want a user to upload a video from our website, would I have to upload the video to our server and then upload it through the API on the server side? |
That's the currently 100% supported flow. We will be releasing client side logic in the future, but for now the closest option is https://github.com/websemantics/vimeo-upload. This library has client side upload, but transmits the access token to the client. Really only the upload url should be transmitted to the client. |
As per vimeo official guide video upload is supported through |
Any news on this? I encountered the same problem. I need to upload a video via my SPA website. I also get the same error even on production whenever I do a |
I am running a local server on localhost:8000 and initializing the library with the clientID, clientSecrets, and accessToken. When I make the streamingUpload API call on a video uploaded by a user, I get the following error messages in my chrome developer console.:
Any idea what might be causing this?
The text was updated successfully, but these errors were encountered: