[Mono-dev] [PATCH] Re: mod_mono AutoConfiguration dead
jit at occams.info
Sat Oct 21 08:15:30 EDT 2006
Gonzalo Paniagua Javier wrote:
> On Fri, 2006-10-20 at 17:57 -0400, Joshua Tauberer wrote:
>> Chris van Wyk wrote:
>>> I am running a FC4 server relying on mod_mono AutoConfiguration.
>>> Unfortunately this died on me today.
>>> I am running ver 18.104.22.168 and will appreciate it if someone could give me a
>>> hint on where to start looking for the problem.
>> Having now taken a look at what's happening, I apologize for breaking
>> Anyway, I'm attaching a patch that seems like it fixes the problem. The
>> problem was twofold. First, virtual hosts seem to not all create a
>> XXGLOBAL (i.e. auto-configuration) mod-mono-server. On my box, I have
>> XXGLOBAls for all of the virtual hosts in which I've explicitly
>> configured the 'default' entry (where I don't use auto configuration,
>> but the configuration gets applied to the XXGLOBAL entry) but not in the
>> virtual hosts that have no explicit AddMonoApplication directives. I
>> don't understand why, but so it is.
> I realized that because when upgrading go-mono.com the configuration
> failed. I think I fixed it in r66836. Can you tell me if that fixes the
> problem for you too?
No, it doesn't. In search_for_alias, what I have coming in is alias =
'XXGLOBAL' and server being a vhost, and what has to happen is it has to
match alias=XXGLOBAL/vhost=NULL just when there doesn't exist an xsp for
alias=XXGLOBAL/vhost=hostname. (Or, we have to ensure we create
separate XXGLOBAL xsp's for each vhost so no fallback would be necessary.)
- Joshua Tauberer
"Strike up the klezmer and start acting like a man. You're
about to have a truth-mitzvah." -- The Colbert Report
More information about the Mono-devel-list