Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create specification for website manifest #176

Open
lidel opened this issue Jan 25, 2021 · 0 comments
Open

Create specification for website manifest #176

lidel opened this issue Jan 25, 2021 · 0 comments
Labels
developers dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks help wanted need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community P1 High: Likely tackled by core team if no one steps up topic/origin Issues related to Origin-based security

Comments

@lidel
Copy link
Member

lidel commented Jan 25, 2021 •
edited
Loading

This is a placeholder to create RFC proposal that improves the experience of publishing websites on IPFS.

  • configuration should live in the content root directory
  • must work on every gateway, so support for "manifest" needs to be implemented in go-ipfs and js-ipfs
  • need to create and agree on spec first

The bare minimum, we need ways to specify some behaviors under the content root (CID used for Origin isolation):

  • redirects (relative, absolute?)
  • content-type
    • where are use cases where people can't use IPFS because their tooling expect specific content-type
    • this should be possible
      • per path (specific file or every file under a directory)
      • per extension
  • some safety-related HTTP headers (eg. [X-Frame-Options](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-- Frame-Options) to disable embedding via iframe or Content-Security-Policy)

Related discussions:
@lidel lidel added help wanted developers dif/expert Extensive knowledge (implications, ramifications) required P1 High: Likely tackled by core team if no one steps up topic/origin Issues related to Origin-based security need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community need/triage Needs initial labeling and prioritization effort/weeks Estimated to take multiple weeks labels Jan 25, 2021
@lidel lidel pinned this issue Jan 25, 2021
@lidel lidel removed the need/triage Needs initial labeling and prioritization label May 14, 2021
@lidel lidel unpinned this issue Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
developers dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks help wanted need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community P1 High: Likely tackled by core team if no one steps up topic/origin Issues related to Origin-based security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lidel