search

WICG / manifest-incubations

Before install prompt API for installing web applications
https://wicg.github.io/manifest-incubations/
Other
98 stars 30 forks source link

Define the fetching model for scope extensions .well-known file #90

Open dmurph opened 10 months ago

dmurph commented 10 months ago

What are the http headers here? Should we include information about the app? What referrer policy should be used?

@LuHuangMSFT

alancutter commented 10 months ago

Is this in service of https://docs.google.com/document/d/1RuxUf8LGbaVfLvIOTorXUa__7cN56r54tQFwd3l45Es/edit#heading=h.tph42uvwe9i ?

dmurph commented 7 months ago

@alancutter - no not in service of that doc, just being explicit about what the fetch model should be I think?

@marcoscaceres Do you mind helping us out for how we might define the headers here / the referrer policy / fetch model? What might we say / reference here?

dmurph commented 1 month ago

@lemanschik I'm not sure I totally understand you - hopefully this answers your question:

This is in regards to https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md

During installation a file is fetched (example: https://example.co.uk/.well-known/web-app-origin-association) on the origins/sites in the scope_extensions field in the manifest. This establishes a two-way handshake to confirm that the origin/site is owned by the same entity as the origin the web app is on.

It might be good to specify how this fetch occurs.

lemanschik commented 1 month ago

@dmurph i was not even aware that this is now a WICG case thanks for enlightening me i was not aware of the complet context but no runtime that i support will support this manifests so i understand now it is out of scope for me. I was under the Assumption that you need some information's about standards.