sfx_base_url in aleph_start
- Article Type: General
- Product: Aleph
- Product Version: 18.01
Description:
I'm going to try to activate SFX in our test region.
If editing ./abc01/tab/tab_sfx, the SFX button does not work - it is always inactive in the Web OPAC Full View,
although the Brief View displays that Full text exists.
when adding debugging to the www_server.conf:
setenv check_sfx_service_1_0 Y
The error in the www_server log file displays the following error:
[..]
HTTP/1.1 500 Internal Server Error
Date: Thu, 12 Mar 2009 18:39:58 GMT
Server: Apache
Alternates: {"500.shtml.en" 1 {type text/html} {language en}}
Vary: negotiate
TCN: list
Content-Length: 715
Content-Type: text/html; charset=iso-8859-1
Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 406 Not Acceptable
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr>
<address>Apache Server at localhost Port 3039</address>
</body></html>
Resolution:
The problem is caused by the trailing slash at the end of the sfx_base_url/instance name in ./alephe/aleph_start.
The POST request should be sent to:
http://sfx.exlibrisgroup.com/instance
not to:
http://sfx.exlibrisgroup.com/instance/
Removing the trailing slash solved the problem.
Additional Information
sfx, sfx_base_url
- Article last edited: 10/8/2013