name based virtual domains

[Anonymous]

as far as i understand…
osx server and virtual domains = port based virtual domains
(e.g. [b:8cf7cebec5]server.one.nnn:100 + server.two.nnn:200[/b:8cf7cebec5] = 2 port based domains on two different ports)
[b:8cf7cebec5]but[/b:8cf7cebec5]
apache can be configured to use name based virtual domains
(e.g. [b:8cf7cebec5]server.one.nnn + server.two.nnn[/b:8cf7cebec5] = 2 name based domains on the same port
question: are the two methods compatible or do i have to choose one or the other?
in my opinion, if i need [b:8cf7cebec5]server.two.nnn[/b:8cf7cebec5] to be more “hidden” it would be better to use name based, since the port based alternative would need protection by name/pass to be “hidden”.
question: how do i enable name based domains while still being able to use Server Settings?

[mischa]

😕

[mischa]

i think i just found the answer myself…
setting up many sites in osx server primarily utilizes name based virtual hosting, since the sites CAN reside on the same port! it is not necessary to assign them to different ports. Doing so is recommended only in one case, if you run a streaming server on port 80 and do not want that to interfere with your web hosting. so — osx server sites must be name based – i will check this tomorrow and verify here.

[mischa]

No – having two sites on the same port# only results in the server serving you the first site with that port# in the config file…
So – I have to ask the question again:

How do i enable name based virtual hosts….?

(my o my…it seem that whatever one needs to do that extends the oh so limited scope of what the server settings allow you to do…you end up leaving server settings alltogether – and use a/manual editing or b/webmin…gruesome)

[mischa]

ok – it does work for me now, but its a workaround:
1. i do not have a bona fide domain registered to my computer where the sites are hosted. all documentation presumes that.
2. i use dyndns -> static dns -> Webhop -> to the ip:port, on a per site basis.
3. then – believe it or not – the name based stuff start to work!
a – ip:port -> you hit the first site in the config-file, never any other site configuret to the same port.
b – name.with.dyn.dns:port – it goes to site named in config, name.with.dyn.dns

for me, nice for now – it gives me time to figure out dns – cuz THAT i cannot figure out.

[Camelot]

[quote:118f037254=”mischa”]a – ip:port -> you hit the first site in the config-file, never any other site configuret to the same port.
b – name.with.dyn.dns:port – it goes to site named in config, name.with.dyn.dns
[/quote:118f037254]

This is exactly what I’d expect.

In option a) you’re hitting an IP address and port. There *is* no server name, so how can Apache know which virtual host you’re trying to hit. It can’t, therefore it serves the default site.

In setup b) where you’re hitting the site by specifying the name, Apache can use that name to determine which virtual host you’re trying to hit and can therefore support multiple sites.

To explain it a bit further, option a is like connecting to the server and saying “give me a page”. Option b is like connecting to the server and saying “give me a page for http://www.yourdomain.com”. There’s nothing in the first option that gives Apache any information about what site you’re trying to get.

[Author]

Posts