Willy Calderon's bits of Fri, 3 May 2002 translated to: >OK, but here's the real problem. The config file(htdig.conf) is configured >to use the output wrapper in >/var/www/htdocs/new/Website/htdig/wrapper.html. This is configured to find >images in /var/www/htdocs/new/Website/images but from the HTML excerpt below, >..... > <tr> > <td height="70" width="1" valign="top"> </td> > <td width="60" valign="bottom"><img >src="../images/barneys/on-home.gif" width="60" height="40" alt="Home" >href="../how_to/how_to.htm"><img src="../images/how-to.gif" width="60" >height="40" border="0" alt="How to"></a></td> ... >Now in the image directories, these .gif files exist. Similarly the >newsroom and how_to directories exist in /var/www/htdocs/new/Website/ >however htsearch seems to be looking for these in the DocumentRoot
I don't think it is correct to state that htsearch is looking for them in any location. You are providing src and href attributes that htsearch simply adds to the result page, just as you specify them. The problem is that these values are not valid in the context of the result page, and thus a browser is unable to successfully retrieve them. >/htdocs/images/on-home.gif). I know that I can place the full path in the >results.html and wrapper.html but surely there has to be a way for htsearch >to 'think' that the img src and a href directories are in the right place >instead of the DocumentRoot directory. Perhaps it is possible, but it doesn't seem reasonable to place such a requirement on htsearch. Pages and images that you reference in your wrapper don't necessarily have anything to do with ht://Dig. In order for it to figure out what ../images refers to it would have to generate a valid URL for your server based on the location of the wrapper file. Even if it managed that, it would then need to rewrite your wrapper file, replacing all of your href's and src's with something that would be valid from the perspective of a typical browser. Keep in mind that your wrapper.html is not a real "web page". It is just a block of HTML code that will be inserted into a page generated by a CGI program. A browser will see that HTML in the context of the generated page, not the context of a static page presented by a web server. With all that said, maybe there is some trick to doing what you want ;) Perhaps something involving the <base> element? I can't answer that one. Jim _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
