Skip to content
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.

Why can I not ignore .well-known/dat? #6

Open
da2x opened this issue Nov 3, 2018 · 2 comments
Open

Why can I not ignore .well-known/dat? #6

da2x opened this issue Nov 3, 2018 · 2 comments

Comments

@da2x
Copy link

da2x commented Nov 3, 2018

Why is this file a hardcoded exception?

It makes no sense distributing this specific file over Dat and doesn’t belong in Dat archives.

@joehand
Copy link
Collaborator

joehand commented Nov 5, 2018

Can you say more about why it doesn't make sense to distribute this file over Dat? @pfrazee may have a bit more perspective here wrt Beaker.

@da2x
Copy link
Author

da2x commented Nov 6, 2018

The file is used to auto-discover a Dat archive/URL from a HTTPS origin/URL. You never need to discover a Dat archive’s own URL from inside the archive since your client obviously already knows it as evidenced by it having already downloaded the .well-known/dat file using the Dat URL. The file is only useful over HTTPS so I really don’t get why it can’t be excluded from Dat archives.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants