Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Discussion: Follow redirects in DNS? #40
Currently the proposal says:
A lookup for dat://www.biserkov.com will hit https://www.biserkov.com/.well-known/dat and everything will work.
But a lookup for dat://biserkov.com will hit https://biserkov.com/.well-known/dat which returns HTTP/1.0 301 Moved Permanently so the lookup will fail.
I believe this situation is quite common, with the current wisdom against apex domains and stuff.
A couple notes:
I find the simplicity of the "no redirects allowed" status quo appealing, but I guess I can't back that up with any reason to break the HTTP(S) "default" of following redirects.
There are several reasons/justifications, I find the one about cookies the most convincing.
No, all browsers seems to have a maximum number. 2012, so a bit dated https://stackoverflow.com/questions/10895406/what-is-the-maximum-number-of-http-redirections-allowed-by-all-major-browsers
I don't know how netlify handles this, but it supports Let's Encrypt and redirects .well-known.
We discussed this in the WG and ultimately decided to give this a "soft no." Our concerns are:
We've decided to leave the issue open so that more people can comment, but we're not going to move forward with the change for now.
Sorry @Biserkov. I appreciate why you'd want this, but we're just concerned about using the DNS layer to do it. Is it possible there's another point in the stack this could be done?