David
Thu Jun 26 04:45:37 CDT 2008
All unassigned is effectively:
*
the catch-all binding.
Wildcard hostheader support has to happen in HTTP.SYS in kernel mode
and not IIS. You'd expect *.domain.com to map to the same Application
Pool in user mode. IIS wouldn't have to do anything. However, *-
bindings are also conflicting with the nature of HTTP.SYS supporting
native HTTP API applications.
The scenario for wildcard host header is not clear to me. In such
shared scenarios, you are interested in user-mode code to dynamically
respond, depending on the host header, and not exactly kernel-mode
request routing, so you might as well use the "unassigned" binding to
do what you want.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jun 25, 11:09=A0pm, "rvj" <r...@rolemodels.net> wrote:
> I read that wildcard hostheaders are not (yet) supported in IIS
> - is the all unassigned option effectively identical to using =A0a wildca=
rd
> host header?
>
> eg *.xyz.com
>
> thanks
>
> "A J Hawke" <a...@lawlessland.co.uk> wrote in messagenews:486130b6$0$2493=
$da0feed9@news.zen.co.uk...
>
>
>
> > On Tue, 24 Jun 2008 17:22:25 +0100, rvj wrote:
>
> >> Does IIS have the ability to trap unknown subdomains for particular
> >> domains ?
>
> >> For example if IIS services multiple domains on the same IP address
> >> using host header files,
> >> then given a particular domain, =A0is it possible to use something lik=
e
> >> wildcards or a custom error handler for that domain via =A0asp code to
> >> trap unknown subdomain requests?
>
> >> thanks
>
> > Use the 'all unassigned' option to direct anything coming in with a duf=
f
> > host header (or none) to a default site.
>
> > --
> > begin =A0broken-news-reader.exe- Hide quoted text -
>
> - Show quoted text -