Super-Guru's question on host header
Fabri
w2k server sp4
iis 5
100+ websites.
For one of these websites (mysite.com) I have to add thousands of host
header as:
download.mysite.com
users.mysite.com
...
and so on.
I am able to program IIS through ADSI to add host header via web
interface, but now I have 5000+ host headers and now to add new one IIS
take 5-6 minutes (really!!!), only ONE.
Please is there a way to catch:
I mean in IIS MMC:
Properties of my website --> Website --> Advanced --> Multiple identies
--> [here put *.mysite.com is not possible :-(]
Please I have to find a solution, whatever is the cost.
--
fabri
Sei un italiano medio, di oltre trent'anni se:
Sai che il codice SYS64738 serviva per riavviare il Commodore 64 ed hai
cambiato almeno una mezza dozzina di joystick Quickshot I giocando a
Summer Games.
MKDS nick & friend Code:
Joker® - 055895 043343
Sanford Whiteman
>interface, but now I have 5000+ host headers and now to add new one IIS
>take 5-6 minutes (really!!!), only ONE.
Ugh. That sucks. I presume you're not on IIS 6; if you are, you
could flip on the direct metabase edit option, go into the XML, dump
all the entries in there, and be done in a flash. With the binary
metabase, that won't be possible.
If you're really in a pinch, what about dedicating a new IP to this
subdomain-centric domain, and setting no host header restriction on
that IP, so it acts like a catch-all? I know it's extreme, but you
said whatever is the "cost." :)
It is also possible to change over your host header scheme, for all or
a selection of your sites, to third-party products such as
ISAPIRewrite and LinkFreeze (www.helicontech.com), rather than IIS'
built-in functionality. If you do this, you have to turn off host
headers at the IIS level (meaning that you consolidate all of the
sites you're doing this for under one IIS virtual host) then use
regular expressions to translate host headers into virtual
directories. The user does not see any of this happening, but it does
represent a major architectural shift for your end. It would give you
what you're looking for, with *.domain.com and domain.com both steered
to the same area, without having to add any specific subdomains
anywhere after you've set it up. But it's gonna cost you (time, not
really much money).
As far as I know, those are the only ways to attack this. If I left
something out, I'm sure someone will chime in soon!
Good luck,
Sandy
Ken Schaefer
a) use a separate IP address (and thus no need for host-headers at all)
b) If you can't use a separate IP address, then use an ISAPI filter. Then
you'd only need a single host-header. The ISAPI filter can rewrite the
incoming Host: header to match the single host-header you have configured in
IIS for that website.
Cheers
Ken
"Fabri" <n...@sp.am> wrote in message news:duonok$cqc$1...@nnrp.ngi.it...
: Scenario: