yacy_search_server/defaults/web.xml
reger b12200cafe alternative UrlProxyServlet (for /proxy.html) using different url rewrite rules
- use JSoup parser for selective rewrite of html body <a href=  links only,
instead of regex which rewrites also header href/src links
- this improves display of pages which use header <base> tag
- tags with src attribute are taken from original location (like css) improving display and are not routed trough the indexer
Disadvantage: scripting links will drop out of proxy

Setting of the servlet through web.xml exclusivly (in case one would like to quickly switch back to the YaCyProxyServlet,
leaving the existing code of YaCyProxyServlet untouched available)
2014-03-30 04:04:02 +02:00

112 lines
4.4 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<!-- Default YaCy web.xml
Note: if DATA/SETTINGS/web.xml exists, it takes preference
-->
<display-name>YaCy</display-name>
<description>Decentralized Web Search</description>
<!-- Standard YaCy Servlets -->
<!-- Default servlet for all YaCy output
-as this is mandatory the servlet is activated automatically by the application
-no need to include this in this web.xml (provided only for completness)
<servlet>
<servlet-name>YaCyDefaultServlet</servlet-name>
<servlet-class>net.yacy.http.servlets.YaCyDefaultServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>YaCyDefaultServlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
-->
<!-- servlet to provide direct access to the embedded solr, also used for P2P searches -->
<servlet>
<servlet-name>SolrSelectServlet</servlet-name>
<servlet-class>net.yacy.http.servlets.SolrSelectServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>SolrServlet</servlet-name>
<servlet-class>net.yacy.http.servlets.SolrServlet</servlet-class>
</servlet>
<!-- servlet to provide Google Search Appliance (GSA) formatted search results -->
<servlet>
<servlet-name>GSAServlet</servlet-name>
<servlet-class>net.yacy.http.servlets.GSAsearchServlet</servlet-class>
</servlet>
<!-- servlet to provide searchresults via proxy and needed for Augmented Browsing -->
<servlet>
<servlet-name>URLProxyServlet</servlet-name>
<!-- replaced with alternative servlet with new url rewrite rules
you may replace the new with YaCyProxyServlet here, to switch back
<servlet-class>net.yacy.http.servlets.YaCyProxyServlet</servlet-class>
-->
<servlet-class>net.yacy.http.servlets.UrlProxyServlet</servlet-class>
</servlet>
<!-- mappings activated by the application - hardcoded (added here for completness) -->
<servlet-mapping>
<servlet-name>SolrSelectServlet</servlet-name>
<url-pattern>/solr/select</url-pattern>
<url-pattern>/solr/collection1/select</url-pattern>
<url-pattern>/solr/webgraph/select</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>GSAServlet</servlet-name>
<url-pattern>/gsa/search</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>URLProxyServlet</servlet-name>
<url-pattern>/proxy.html</url-pattern>
<url-pattern>/proxy</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>SolrServlet</servlet-name>
<url-pattern>/solr/collection1/admin/luke</url-pattern>
<url-pattern>/solr/webgraph/admin/luke</url-pattern>
</servlet-mapping>
<!-- eof hardcoded mappings -->
<!-- additional (optional) mappings -->
<!-- you may add individual mappings of standard servlets here also -->
<!-- eof additional (optional mappings -->
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>Index.html</welcome-file>
<welcome-file>Welcome.html</welcome-file>
</welcome-file-list>
<!-- security configuration -->
<!-- authentication method and default roles are preconfigured by the application (provided only for completness) -->
<login-config>
<!-- supported BASIC or DIGEST -->
<!-- Note: with DIGEST the name of this peer is part of password hashes
changing the peer name will invalidate all passwords
!!! Attention !!! prior to change this to DIGEST you have to reenter your password
to calculate a correct password hash -->
<auth-method>BASIC</auth-method>
</login-config>
<!-- Roles -->
<security-role>
<role-name>adminRight</role-name>
<description>Administrator</description>
</security-role>
</web-app>