Skip to main content.
home | support | download

Back to List Archive

Re: Documentation on Swish-E working with Apache and SSL

From: Bill Moseley <moseley(at)not-real.hank.org>
Date: Fri Jan 23 2004 - 19:46:39 GMT
On Fri, Jan 23, 2004 at 09:34:19AM -0800, Kaplan, Andrew H. wrote:
> 
> When the swish.conf file is used as a configuration mechanism for the
> Swish program, it typically contains a ReplaceRules line that
> references the hostname or ip address of the host server. Figure One
> shows a sample swish.conf file with the line in question highlighted.
> 
> Figure One:
> 
> ReplaceRules replace "/usr/local/apache/htdoc/"  "http:/example.com/documents/" 
> 
> There are occasions when an administrator will configure the
> webserver, as a matter of security, to have all connections default to
> the Secure Sockets Layer (SSL) port 443. When this is done, the above
> configuration would cause the files to become inaccessible. A query of
> the files would result in a list being displayed on-screen, but a
> subsequent request to pull up the files would fail. 
> 
> The solution to this problem is to modify the swish.conf file to
> reflect the secure connection to the webserver, rerun the indexing,
> and, if necessary, restart the server. Figure Two shows the above file
> modified as such.
> 
> Figure Two:
> 
> IndexDir /usr/local/apache/htdoc
> StoreDescription HTML * <body> 200000
> MetaNames swishdocpath swishtitle
> ReplaceRules replace "/usr/local/apache/htdoc/"  "https:/example.com/documents/" 

How about Figure Three:

  ReplaceRules replace /usr/local/apache/htdocs /documents

Will that work?


-- 
Bill Moseley
moseley@hank.org
Received on Fri Jan 23 11:46:44 2004