As far as I can tell, it's only due to the limitation of A/PTR resource record mismatches that SSL doesn't work on host-header. The SSL key is actually registered under a domain name, not an IP address.
Yep, address shortages are the reason; due to the numbers of hoarded addresses, many NICs have nothign to do but hoarde more addresses. That's not to say that there's not alot of un-allocated CIDR blocks sitting out there, however...
http://www.stu d.ifi.uio.no/~lmariusg/download/artikler/HTTP_tut. html read that, it explains the HTTP protocol. Basically, host header webservers host multiple sites (different domain names, e.g. "http://www.example.com" and "http://www.fred.com") on the same IP address. They distinguish between which site to send to the client based on the HTTP request itself, rather than purely the DNS lookup.
APNIC (Asia Pacific NIC) has had a "move to host header" policy for awhile now, and when we ask for more addresses (we presently have a request for a large block in with them), they want to see your network address plan, and they want to see how many host header boxes versus how many IP'd webservers you have.
Host header, as dirty a word as it is, seems to work fine (we use Micro$oft IIS, ugh) - oh. there's one sticking point. You cant use bundle per-virtual-server anonymous FTP access on the domain name to clients. This minor problem aside, I think it's a good thing. The number of borign web sites we have wasting IP addresses haunts me every time I open that address database...
I dont think you guys are seeing the upside to this. Every time I hear a record I know where the loop is from, I wont have to go hunting through a couple of hundred Candido or James Brown records to find that "Clyde Stubblefield after 6 bucket-bongs" loop, the server in the corner can do it for me.
Then I really will have "too much time on my hands"..:)
Anyone who has ever had to deal with re-delegating an.org.au domain (Elz manages the.org.au namespace, personally, in his spare time, like he used to do with.com.au) will be glad when the guy has nothing to do with it anymore (early 2001). Waiting six months for a re-del is a bit of a piss-take, if you ask me. However, he doesn't seem like too bad a guy (hell, Sun gave him a box in 1991 for the hostmaster archie.au because he whined enough:-), but he does take his bloody time.
Also, his sense of humour is definately acquired - reas his "humorous" RFCs if you want an example:-).
Slashdot Mirror
As far as I can tell, it's only due to the limitation of A/PTR resource record mismatches that SSL doesn't work on host-header. The SSL key is actually registered under a domain name, not an IP address.
Yep, address shortages are the reason; due to the numbers of hoarded addresses, many NICs have nothign to do but hoarde more addresses. That's not to say that there's not alot of un-allocated CIDR blocks sitting out there, however...
http://www.stu d.ifi.uio.no/~lmariusg/download/artikler/HTTP_tut. html read that, it explains the HTTP protocol. Basically, host header webservers host multiple sites (different domain names, e.g. "http://www.example.com" and "http://www.fred.com") on the same IP address. They distinguish between which site to send to the client based on the HTTP request itself, rather than purely the DNS lookup.
Host header, as dirty a word as it is, seems to work fine (we use Micro$oft IIS, ugh) - oh. there's one sticking point. You cant use bundle per-virtual-server anonymous FTP access on the domain name to clients. This minor problem aside, I think it's a good thing. The number of borign web sites we have wasting IP addresses haunts me every time I open that address database...
Then I really will have "too much time on my hands".. :)
Also, his sense of humour is definately acquired - reas his "humorous" RFCs if you want an example :-).