-
Notifications
You must be signed in to change notification settings - Fork 6
Chrome extension file access issues #18
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
Comments
You can upload files to our file server using Fetch API:
Then use the uploaded file ID in the conversion request. |
And what if there are multiple authorization headers? |
For such exotic scenarios, I would use FaaS (Cloudflare workers, Amazon functions) to add these headers. |
Just found out that is not yet implemented. So for now use FaaS solution. |
I have never heard of this FaaS solution before. Any chance you could link some documentation or a guide? |
Using https://unpkg.com/convertapi-js/lib/convertapi.js
I guess this is more of a feature request. I am trying to write a chrome extension that grabs some image URLs then uses this API to convert it to PDF. My problem is that the files are protected behind authorization headers. When I use
new URL
it removes the authorization headers and the request fails. I am willing to modify my local copyconvertapi.js
if needed.I have tried (for several hours) to use the file type instead, but it looks like you need to use the actual
File
object type and I cannot get this in a chrome extension as far as I know. Because, if I try to download the files it only gives me the downloadId. If you have suggestions for alternatives I would be happy to try them. Creating this issue is my last resort so hopefully there is some way I can get this to work.The text was updated successfully, but these errors were encountered: