Mark Andrews wrote:
Transitioning HTTPS to use SRV is complicated because of proxies.
There needs to be changes to how clients talk to proxies for HTTPS
+ SRV to work through proxies.
CONNECT server.example.org:100 HTTP/1.1
I was referring to this sort of misuse.
www.example.com CNAME server.web-hosting-service.com.
www.example.com really isn't a alias for server.web-hosting-service.com
If it was you could replace "www.example.com" with
"server.web-hosting-service.com" and be served the same content.
Or this misuse
example.com SOA ...
example.com MX ...
example.com CNAME server.web-hosting-service.com.
Do you mean there is no complication of HTTPS+SRV by proxies?
which people try to do and causes all sort of problems.
Your examples just do not work for people, which will drive them
solve their own problems by themselves.
Ietf mailing list