Although not released until 10 January 2006, this release was prepared prior to Autonomy’s acquisition of Verity on 1 January 2006. It’s a fairly big release, with some important under the cover features. NTLM Indexing / Filtering support Ultraseek 5.5 can now index sites protected with NTLMv2. When using hit-level authentication, Ultraseek can now filter results by passing NTLM credentials between the browser and each site with protected content. This feature is enabled by the “Acquire user credentials via NTLM” checkbox. User credentials will be automatically transmitted if the browser is configured to do so. In Internet Explorer, this is configured in the Internet/Security tab. In Firefox/Mozilla, this can be configured on the about:config page by adding the Ultraseek site to the network.automatic-ntlm-auth.trusted-uris variable. You should also raise the value of the network.http.redirection-limit variable to at least 30. When Ultraseek uses NTLM to acquire user credentials, filtered result sets will not include hits that are protected with Basic authentication. That is to say, do not turn on this feature if your collection contains both NTLM and Basic protected content. This feature requires the use of HTTP keep-alives. Performance improvements Query performance has been improved. In particular, query interfaces using Passage Based Summaries or spelling suggestions have improved latency and throughput. Ultraseek 5.5 uses a cache to re-serve the HTML result pages for duplicate queries. The cache is automatically cleansed when document indexes or other configuration is changed on the Ultraseek server. You can flush it manually with the Admin UI: Server>Parameters>Reload button. Ultraseek’s HTML compiler now supports NCSA Server-Side-Include syntax. Other enhancements The “check” button under Server>Quick Links performs validation checks on your Quick Link definitions (such as checking the target URL). The text of a ‘title’ attribute on an href is now indexed as anchor text. The mappings that allow terms with extended Latin characters to be found by searching with simplified basic Latin (ASCII) characters are now language-dependent and customizable. For example, o with umlaut matches a search for oe in German, but not in Swedish. The characters which should not be matched to simplified forms for a given language are listed in the .xml file, in the extchars element. Scripted Python/HTML pages now run in a page context similar to a Python module. Existing /doc sets will not notice any change. Supported platforms

• Microsoft Windows 2000, Windows 2003, Windows XP Professional (Intel compatible)
• Solaris 8, Solaris 9 (SPARC)
• Suse Linux 9.0 (Intel compatible)
• Red Hat Enterprise Linux 3.0 (Intel compatible)