httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guenter Knauf <fua...@apache.org>
Subject Re: Different vhosts.conf between Apache 2.2.17 for Windows and Apache for Linux 2.2.14-rc1 - issue 25435?
Date Thu, 10 Feb 2011 09:22:39 GMT
Hi Zeno,
Am 10.02.2011 09:48, schrieb Zeno Davatz:
> It seems that Apache for Windows interprets vhosts.conf files
> differently then Apache for Linux does. I am asking this question
> related to mod_ruby. Both Apaches (Linux and Windows) start fine with
> mod_ruby.so loaded.
>
> This vhosts.conf file on Linux Apache 2.2.14-r1 works just fine. Ruby
> is executed:
>
> https://gist.github.com/820139
>
> this vhosts.conf file on Windows Apache 2.2.17
>
> https://gist.github.com/820138
>
> delivers the index.rbx file as plain text instead of executing it as
> Ruby-Script. The vhosts.conf file was modified because of below issue.
> It seems to me that this is connected to this issue here:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=25435
>
> Is it normal, that a vhosts.conf on Linux can _not_ be assumed to work
> on Windows as well? Or is this an issue with mod_ruby not yet working
> correctly with Apache for Windows? Ruby is in my System path on
> Windows.
I have not (yet) looked at your links, but want to give you another hint 
which might (or not) reveal some differences between your Linux and 
Win32 installation: load mod_info on both boxes, and try to compare the 
config directives; usually if you use a httpd from Linux distro the 
configuration is splitted into several config files, and also distros 
come along with their own modified mime.types and magic files ...
this can all cause different behaviour ...

Gün.



Mime
View raw message