-
I am developing a chrome extension which will send requests to Appwrite using client SDK or REST API (the usual Appwrite doesnt accept any kind of client side requests from origins like "chrome-extension://" 👟 Reproduction steps
IMPORTANT: I was able to call createOAuth2Session (Accounts API) for Auth that means the extension can send fetch requests no problem and the Web SDK works fine. But, Appwrite needs to whitelist "chrome-extension://" origin to make these requests happen.🎲 Appwrite versionAppwrite Cloud 💻 Operating systemLinux 🧱 Your Environmentappwrite websdk version: 11.0.0 👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Having a setting to whitelist the I cant even execute appwrite functions to make requests on behalf of my client (chrome extension). Atleast, appwrite functions should have this "whitelist origin" feature.
|
Beta Was this translation helpful? Give feedback.
-
Thanks Steven for your help in discord. Solution:- |
Beta Was this translation helpful? Give feedback.
Thanks Steven for your help in discord.
Solution:-
from
chrome-extension://<extension-id>
add
<extension-id>
as hostname in web platform