[greenstone-users] Problem accessing graphics

From Katherine Don
DateMon Aug 30 13:54:44 2010
Subject [greenstone-users] Problem accessing graphics
In-Reply-To (4C7316CE-2060005-free-fr)
Hi John

I don't think that changing DocumentRoot is necessary. With our bundled
apache, we have the DocumentRoot pointing to a subfolder inside where
apache is installed.
Alias is used to let apache access the greenstone images which are
located outside DocumentRoot.

The customised bits for Greenstone are just the ScriptAlias and Alias
bits at the end of the bundled apache's httpd.conf,

ScriptAlias /greenstone/cgi-bin
<Directory "/research/kjdon/home/z3950/greenstone2/cgi-bin">
Options None
AllowOverride None
Order allow,deny
Allow from all


Alias /greenstone "/research/kjdon/home/z3950/greenstone2"
<Directory "/research/kjdon/home/z3950/greenstone2">
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all

I think that if you have a plain apache set up and working, and you add
the appropriate sections as above, then it should work without changing

Perhaps you have some different/custom settings in your own apache's
conf file?


John Rose wrote:
> Hello,
> Using Greenstone 2.82 under Windows Vista I had no problem accessing
> Greenstone through my existing Apache server on the same machine
> (using the httpd.conf parameters in the Intaller's Manual). However
> when I installed Greenstone 2.83 in my home directory and removed the
> apache-hppd directory for the bundled Apache server, although I could
> access Greenstone via Apache the graphics did not show (even when I
> used the httpd.conf parameters from the bundled Apache, which are
> nearly the same as in the Manual).
> This problem can be solved by replacing the line:
> DocumentRoot "C:/Program Files/Apache Software
> Foundation/Apache2.2/htdocs"
> by
> DocumentRoot C:/Users/John [my Windows home directory]
> That is, even though I have an index.html file in the Apache htdocs
> directory, the default httpd.conf paramaters do not work.
> I suggest that this problem be clarified in version 2.84, either by
> changing the default Apache parameters and/or the user documentation.
> Best regards, John