Hi All, The image src url in the LAS product is generated from the APACHE ENV variables SERVER_NAME and SERVER_PORT. I'm not sure how your apache httpd.conf file sets these. It can be explicit or automatic. Also, in your /etc/hosts file, I think 'localhost' should be assigned to 127.0.0.1, not the IP address of your computer 127.0.0.1 localhost.localdomain localhost see http://www.accs-net.com/hosts/what_is_hosts.html for information on the hosts file. Joe ----------------------- Ben Burford wrote: Hello Phil, Your examples from a working system are really helpful. I'm sure we're very close to the solution, but not quite there yet. I'm not sure if httpd.conf or any of the other files are correct. I think they are, but I'm learning a lot in this process. I'll give you content to various files that you've referred to (and a few ot hers). The contents of my hosts file (/etc/hosts) is: # Do not remove the following line, or various programs # that require network functionality will fail. 172.16.7.82 rdtest localhost.localdomain localhost 172.16.7.82 rdtest The contents of my config.results file (under /usr/local/las/las) is: $LasConfig{db_host} = 'rdtest'; $LasConfig{title} = 'WTF-CEOP'; $LasConfig{uipath} = '/las'; $LasConfig{group} = 'nobody'; $LasConfig{hostname} = '172.16.7.82'; $LasConfig{fullpath} = 'http://172.16.7.82/las-bin/LASserver.pl'; $LasConfig{java} = '/usr/java/j2sdk1.4.2_04/bin/java'; $LasConfig{fullpath_output} = 'http://172.16.7.82/las-output/LASserver.pl'; $LasConfig{webapps} = 'las_servlet/jakarta/webapps'; $LasConfig{jakarta_home} = 'las_servlet/jakarta'; $LasConfig{pathname} = '/las-bin'; $LasConfig{apache} = '1'; $LasConfig{perl} = '/usr/bin/perl'; $LasConfig{ferret} = '/usr/local/ferret/bin/ferret_v560'; $LasConfig{output_alias} = '/las-output'; $LasConfig{custom_name} = 'custom'; 1; I think my system uses /las-output/ rather than /lasxml-output/ so I think t hese two lines are OK: $LasConfig{fullpath} = 'http://172.16.7.82/las-bin/LASserver.pl'; $LasConfig{fullpath_output} = 'http://172.16.7.82/las-output/LASserver.pl'; My httpd.conf file contains: Alias /las-output/ /usr/local/las/las/server/output/ and it also contains: ScriptAlias /las-bin/ /usr/local/las/las/server/ I was instructed by the LAS installation configure file to put these two lin es into httpd.conf. On my server in the /usr/local/las/las/server/output directory are pairs of gif images and html files, e.g.: -rw-r--r-- 1 apache apache 24957 Jun 14 14:56 68321cd073c6ecf8877 1c9d824e19672.gif -rw-r--r-- 1 apache apache 340 Jun 19 19:09 68321cd073c6ecf8877 1c9d824e19672.html In the contents of 68321cd073c6ecf88771c9d824e19672.html I see: <table> <tr> <td> <img border="0" src="" class="moz-txt-link-rfc2396E" href="">"http://localhost:80/las-output/68321cd073c6ecf88771 c9d824e19672.gif"> </td> </tr> </table> In the source of the html page on my Internet Explorer browser I see: <table> <tr> <td> <img border="0" src="" class="moz-txt-link-rfc2396E" href="">"http://localhost:80/las-output/68321cd073c6ecf88771 c9d824e19672.gif"> </td> </tr> </table> and further down in the html page is: </td></tr> <tr><td align="center"> <a target="_blank" href="" class="moz-txt-link-rfc2396E" href="">"http://172.16.7.82/las-bin/LASserver.pl?x ml=%3C%3Fxml+version%3D%221.0%22%3F%3E%3ClasRequest+package%3D%22%22+href%3D %22file%3Alas.xml%22+%3E%3Clink+match%3D%22%2Flasdata%2Foperations%2Fshade%2 2+%2F%3E%3Cproperties+%3E%3Cferret+%3E%3Csize+%3E.5%3C%2Fsize%3E%3Cformat+%3 Eshade%3C%2Fformat%3E%3C%2Fferret%3E%3C%2Fproperties%3E%3Cargs+%3E%3Clink+ma tch%3D%22%2Flasdata%2Fdatasets%2Fcoads_climatology_cdf%2Fvariables%2Fairt%22 +%2F%3E%3Cregion+%3E%3Crange+low%3D%22-180.0%22+type%3D%22x%22+high%3D%22180 0%22+%2F%3E%3Crange+low%3D%22-89.0%22+type%3D%22y%22+high%3D%2289.0%22+%2F% 3E%3Cpoint+v%3D%2215-Jan%22+type%3D%22t%22+%2F%3E%3C%2Fregion%3E%3C%2Fargs%3 E%3C%2FlasRequest%3E" title="Permanent link to this plot/data">Permanent lin k to this plot/data</a> </td></tr> So, when LAS creates the html for the output page it is putting in: http://localhost:80/las-output/68321cd073c6ecf88771c9d824e19672.gif and my IE browser doesn't know where on the local lan to find "localhost". But LAS is clearly aware of the correct address, i.e.: $LasConfig{fullpath_output} = 'http://172.16.7.82/las-output/LASserver.pl'; in the config.results file, and: http://172.16.7.82/las-bin/LASserver.pl?xml= . . . in the html page. So las-bin is resolved to "172.16.7.82", but las-output i s resolved to "localhost:80". So, what is the LAS software that is putting this next line in the html outp ut page?: <table> <tr> <td> <img border="0" src="" class="moz-txt-link-rfc2396E" href="">"http://localhost:80/las-output/68321cd073c6ecf88771 c9d824e19672.gif"> </td> </tr> </table> and why is it using "localhost" instead of resolving it to 172.16.7.82? Anything else you can think of for me to check? Thanks very much, Ben At 11:34 2004/06/18 -0700, you wrote:Ben, I wanted to touch back on the output alias for apache. In your config.results file you should have a line similar to the following: $LasConfig{fullpath_output} = 'http://ecco-las.ucsd.edu/lasxml-output/LASserver.pl' The directory "lasxml-output" is the directory which will need to be aliased out in the apache config with a line similar to the following: Alias /lasxml-output/ /las/apache/www/org.ecco-group.www/lasxml/server/output/ Is your output directory "/usr/local/las/las/server/output" aliased out in the httpd.conf file? Hopefully this helps, I am trying to think of anything that may be holding you up there. Phil |