On Wed, Jan 07, 2004 at 09:53:16AM -0500, Kaplan, Andrew H. wrote:
> Hi Bill --
> 
> I modified the swish.cgi and swish.conf files and I have made some progress.
> 
> The links no longer have the NULL statement. However, the files are still 
> inaccessible. When I check the URL for the file, it indicates the file is 
> in the cgi-bin directory when in reality it is in the documenation
> directory.

I think I answered this question already.  Please re-read that response.

> The swish.cgi file is located in the cgi-bin directory, and the swish.conf 
> file is in the documentation directory.
> 
> When I created the index, I was in the documentation directory

If you index files relative to one directory then obviously you can't 
access them relative to another directory.  That's exactly why the 
config option "ReplaeRules" and the swish.cgi "prepend_path" features 
exist -- as I said last time.

> I've included the two files in this e-mail.

I love Windows:

[-- Attachment #3: swish.conf.rtf --]
[-- Type: application/rtf, Encoding: base64, Size: 0.4K --]

[-- application/rtf is unsupported (use 'v' to view this part) --]


You have:

   ReplaceRules remove /www/documentation/\par

So that removes that prefix.  Not sure what that \par thing is.
I'm not saying that's right or wrong -- you have to determine if it's 
doing what you want.

Then in swish.cgi.rtf you have:

  #prepend_path    => 'http://localhost/mydocs',\par

Again, there's that \par thing.  Anyway, to add a prefix of, say 
/documentation you would use:

  prepend_path => '/documentation',

or if you wanted to specify the host, too:

  prepend_path => 'http://my.host/documentation',

> The 'spaces' that I mentioned in the previous e-mail refer to the filenames.

Yes, that's what I assumed.  So what's the problem?  And don't tell me,
show me with small (pasted text) examples.


-- 
Bill Moseley
moseley@hank.org