You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the nuxt-image package utilizes IPX as the image server. While validating the "domains" to prevent abuse, I discovered that if we store images in a collective domain, it becomes challenging to prevent abuse effectively. For instance, if we place images in Google Storage without setting up a dedicated domain (setting up a dedicated domain would not provide SSL services and requires an additional CDN), for example, https://storage.googleapi.com/bucketA and https://storage.googleapi.com/bucketB, it becomes impossible to differentiate them using the "domains" setting.
Describe the feature
I noticed that the nuxt-image package utilizes IPX as the image server. While validating the "domains" to prevent abuse, I discovered that if we store images in a collective domain, it becomes challenging to prevent abuse effectively. For instance, if we place images in Google Storage without setting up a dedicated domain (setting up a dedicated domain would not provide SSL services and requires an additional CDN), for example, https://storage.googleapi.com/bucketA and https://storage.googleapi.com/bucketB, it becomes impossible to differentiate them using the "domains" setting.
Reference: nuxt/image#919
Additional information
The text was updated successfully, but these errors were encountered: