Ben Ramsey on Nostr: A well-known URI defining params around which paths of your site opt-in to how they ...
A well-known URI defining params around which paths of your site opt-in to how they are used. The server uses this to decide how to serve the content, and the requestor must include a request header indicating how it intends to use the content.
Browsers, bots, etc. would have to include the header with appropriate value for their use. Server would decline access by default to requests not including the header, but you could set up the well-known URI to allow access.
Could it work?
Browsers, bots, etc. would have to include the header with appropriate value for their use. Server would decline access by default to requests not including the header, but you could set up the well-known URI to allow access.
Could it work?