Dear Tom Thanks for the reply. On Wed, Feb 9, 2011 at 5:22 PM, Tom Evans <tevans.uk@xxxxxxxxxxxxxx> wrote: >> This is my mod_ruby.conf settings on Linux and there it just works fine: >> >> LoadModule ruby_module modules/mod_ruby.so >> >> # taken from the example file >> # If the ruby module is installed, this will be enabled. >> # for Apache::RubyRun >> RubyRequire apache/ruby-run >> >> # exec files under /ruby as ruby scripts. >> <Location /ruby> >> SetHandler ruby-object >> RubyHandler Apache::RubyRun.instance >> Options ExecCGI >> </Location> >> >> # exec *.rbx as ruby scripts. >> <Files *.rbx> >> SetHandler ruby-object >> RubyHandler Apache::RubyRun.instance >> </Files> >> >> So if you mean this "Options ExecCGI" then yes, to my understanding >> Ruby is executed as CGI on Apache, at least on Linux it is. > > OK. That config is WAAAAAY different to your posted windows config. In > your windows config, you have "SetHandler ruby-object" at the vhost > level, on linux you do not. It's a big difference! This is my vhosts Linux config: https://gist.github.com/818788 > According to [1], ExecCGI is only required for eruby. Well it is in our Linux mod_ruby Config as well and we do not use Eruby. >> Now Apache on Windows delivers me the same result (as so is the following) >> >> [error] [client 127.0.0.1] Attempt to serve directory: >> C:/Users/zdavatz/de.oddb.org/doc/ >> >> with these settings here: https://gist.github.com/818654 >> >> This option here https://gist.github.com/818519 I just tried to see if >> I get the same result or not. > OK, replace your vhost conf file with this one[2]. Does that work? Thanks for the file. This just displays me the content of my index.rbx as plain text but ruby is not actually executed. The access log tells me: "GET / HTTP/1.1" 304 - Best Zeno --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|