allow domain validation with subpaths
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
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: https://github.com/nuxt/image/issues/919
Additional information
- Would you be willing to help implement this feature?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named in the issue. Start by reviewing IPX's current domain validation and the referenced nuxt/image issue 919; done means the domains setting can distinguish paths such as storage.googleapi.com/bucketA and storage.googleapi.com/bucketB without weakening abuse prevention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100