# REL 6, 20070906 - Requires PAPI >= 1.4.1 # Remote_Domain isiknowledge.com # Some ISI pages use broken tags, so the new PAPI >= 1.4 XHTML parser gets # confused No_XML 1 # Mark URI-escaped characters PAPI_Redirect %(25)?([0-9a-fA-F]{2}) *$1$2* # Normal references PAPI_Redirect ([\w]+)\.isiknowledge.com $papx_hostname/$1/ PAPI_Redirect (/|\*2F\*)isiknowledge.com $1$papx_hostname/www/ # URLs with port spec PAPI_Redirect $papx_hostname/([\w]+)(/|\*2F\*)?(:|\*3A\*)(8080)(/|\*2F\*) $1.isiknowledge.com$3$4$5 PAPI_Redirect $papx_hostname/([\w]+)(/|\*2F\*)?(:|\*3A\*)([\d]+)(/|\*2F\*) $papx_hostname$3$4$5$1$5 PAPI_Redirect $papx_hostname/(/|\*2F\*)?(:|\*3A\*)([\d]+)(/|\*2F\*) $papx_hostname$2$3/$papx_namedest$4 # Rewrite back "product references" into URL params PAPI_Redirect product_st_thomas=(.*?)$papx_hostname(:|\*3A\*)?([\d]+)?(/|\*2F\*)(.*?)(/|\*2F\*) product_st_thomas=$1$5.isiknowledge.com$2$3$4 # Rewrite back "product references" in direct URLs (forms) PAPI_Redirect ^http://$papx_hostname(:[\d]+)?/([\w]+)/(.*?)StThomas(.*?)$ http://$2.isiknowledge.com$1/$3StThomas$4 PAPI_Redirect ^http://$papx_hostname(:[\d]+)?/st([\d]+)/(.*?)$ http://st$2.isiknowledge.com$1/$3 # Deal with back references in the case of journal lists PAPI_Redirect ^http://$papx_hostname/(.*?)/mjl/(.*?)\?(.*?)&rurl=(.*?)$papx_hostname(:[\d]+)?/([\w]+)(.*?)$ http://$papx_hostname/$1/mjl/$2?$3&rurl=$4$6.isiknowledge.com$5$7 # Unmark URI-escaped characters PAPI_Redirect \*(25)?([0-9a-fA-F]{2})\* %$1$2 # Relative links PAPI_Redirect http://$papx_hostname/([\w]+)/(.*?)(\.\./)+(.*?) http://$papx_hostname/$1/$4 # Final clean-up of extra slashes (avoid problems in cookie paths) PAPI_Redirect $papx_hostname(/|\*2F\*)([\w]+)(/|\*2F\*){2} $papx_hostname$1$2$3 PAPI_Redirect isiknowledge.com(/|\*2F\*){2} isiknowledge.com$1$2$3 # Only to allow the "st_thomas" in marked lists accesded through CrossSearch # to be correctly rewritten. PAPI_Redirect http://$papx_hostname/estiedcpub/esti/xrpc http://estiedcpub.isiknowledge.com/esti/xrpc # Add here any references for other PAPI proxies to allow the # use of "full text access" features # # An alternative interface can be built using the PAPI proxy just # to load the access cookies into the browser # Bear in mind that using this interface will not allow the use of # the rewriting capabilities inside your isiknowledge.com connection, # so the "full text access" features will not be redirected to other # PAPI proxies Remote_Domain isiknowledge.com PAPI_Redirect ([\w]+).isiknowledge.com/(.*?)Func=Menu $papx_hostname/$1Func=Menu PAPI_Redirect ([\w]+).isiknowledge.com/portal.cgi$ $papx_hostname/$1/portal.cgi