> -----Original Message-----
> From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]] 
> 
> Another case for language impedance? ;)..
>

Yes it seems :)
 
> 
> > But what if I wish that nothing from the default host be the Global
> > mapping.
> 
> I dont think i understand you completely, but from my POV, it's
> irrelevant, we do want Global mappings? i think so, this is the way
> I_r.dll works right now, and we need to map such a functionality.
>

You may have a VS that you wish NOT to map. But OK, then you have to
name that host withouth any mappings.


> > 1. Make the alias to work
> 
> Ohh, never tried, are aliases buggy too? :))
>

Don't know how that happened, but yes :-).

> 
> > 2. Get rid of Global settings as such (but can be enabled if 
> > you put the
> > vhost as a alias to the default host)
> 
> This makes life very complicated to old i_r users, neither 
> it's the best
> for a mass vhosting enviroment.. until a better solution, i'm -1 in
> unsupport Global mappings..
> 

OK, I can live with that for now :)

> > 3. Make the host:port parsing to work 
> 
> ok
> 

I'm working on that for some time, using also *:* parsing, meaning that
the default host will have the vhost name as "*", allowing mappings
either to that or to the NULL (allowing Global mappings). So intead of
NULL and separate table we'll use the "*" for a host name and only vhost
tables.
It will make the entire code lot easier to understand. Is that OK with
you?

Could you check the i_r2.dll if it can use the GetServerVariable
SERVER_NAME:SERVER_PORT perhaps?


MT.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to