Cross-site loads of signed packages should be done stateless and with no personalization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
As brought up by @cramforce in https://github.com/WICG/webpackage/issues/422#issuecomment-485054801, we should require cross-site loads of signed packages to be stateless. Specifically:
- The request chain must be credential-less. Maybe we can leverage some Fetch policy here.
- It must be an HTTP GET request.
- The request URL must not have a query string or fragment.
- The path of the package request must be the same as the path on the target domain.
The above requirements are to ensure that cross-site tracking or personalization information is not transferred in the request for the package.
Contributor guide
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
Start with the linked discussion in issue 422 and determine where the webpackage specification defines cross-site package requests. Done means the specification clearly requires credential-less request chains, HTTP GET, no query string or fragment, and a matching request path, while preventing cross-site tracking or personalization.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100