In message
<4E290442(_dot_)3010402(_at_)necom830(_dot_)hpcl(_dot_)titech(_dot_)ac(_dot_)jp>,
Masataka Ohta writes:
Mark Andrews wrote:
Transitioning HTTP to use SRV is trivial even with proxies.
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.
What's wrong with:
https://www.example.com
_https._tcp.www.example.com SRV 0 1 100 server.example.org
CONNECT server.example.org:100 HTTP/1.1
Host: www.example.com
?
HTTP and HTTPS's use of the DNS is a abomination. CNAME is totally
misused. If you want to host a service on another machine you use
a record that indicates that. You don't use a alias because aliases
mean so much more.
What's wrong with:
https://www.example.com
_https._tcp.www.example.com SRV 0 1 100 server.example.org
server.example.org CNAME cname.example.org
Firstly SRV is not (yet) defined for HTTP.
CONNECT server.example.org:100 HTTP/1.1
Host: www.example.com
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.
which people try to do and causes all sort of problems.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka(_at_)isc(_dot_)org
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf